Based on https://github.com/meteor/meteor/blob/devel/tools/isobuild/package-source.js#L1303 these addintoal folders are ignored but not documented. Some of them may be intentionally left out of the documentation but I'm just suggesting adding documentation for all that seem appropriate.
I tried to reuse the phrase "not loaded anywhere" even if it's a bit awkward phrasing, I think. I wasn't sure if the Meteor file gobbler (as I like to call it) should be called an "autoloader" or something else...
[stubailo: squashed and improved]
This simply adds an extra note to the 'writing packages' section of the docs which states that you should `meteor add` an internal package to enable it. I ran into this issue and banged my head for a while last night wondering why an internal package was not exposing a template / exported object to the rest of my app. The issue was that I did not `meteor add` it since I assumed that because it was internal source code I did not have to.
`var x = function () {}` creates a reference to an anonymous function while `var x = function x () {}` creates a reference to a named function. I believe that `function x () {}` is shorthand for the latter.
