Update: The Meteor Manual has been updated and now contains the loading order for Styles 1.2 and 1.3 and special reference information. Here
server - works only on the server
client - only sent to client
customer / compatibility. Download first in front of other normal javascript files, put jquery, bootstrap, etc. here if you have any problems with them elsewhere
public - Static files / assets, such as images, music, etc., available to the user
public / online - a folder that will not be cached when configured on
private - Static files / assets are available only for the server
import - Files are downloaded only when using the import command.
node_modules - used by NPM for node modules, separated from meteor.
tests - Files for tests - do not load anywhere.
lib - loaded on both clients, loaded to another code
Any other folder (of which I know) is not a special folder, but it is downloaded by both the server and the client. Launch is not special, but it is a standard used by developers to indicate that the files in it are related to the launch of the application, for example, configuration files or files.
You can use any folder name that you want that is not specially processed, and it will be downloaded both on the server and on the client.
The recommended way to use Meteor now is to use the import directory and only import code when and where you need to control the flow and load order.
It is annoying that they removed this list from Meteor docs. One of the commentators found a link to old documents: http://devdocs.io/meteor/index#structuringyourapp Update . The link now points to a new meteor guide.
source share