Meteor package structure (client / server)

Question

I am creating a meteor pack. I noticed that in the package, even if I put my code in the server directory, the code starts the client. What is the pattern used in packages to split code? Should I rely only on packaging the code with Meteor.isServer? Is there any configuration for package.js?

Answer 1

Packages do not rely on a specific application-level file structure responsible for conditional loading and download order; on the contrary, you must specify which files are downloaded first and on which architecture.

You can do this using the package APIs, in particular use this:

https://docs.meteor.com/#/full/pack_addFiles

Package.onUse(function(api){
  // ...
  api.addFiles("server/server.js","server");
  // ...
});

/, , / .