[Solved] Nested import under Meteor.isServer still included in client bundle

[abecks]

I have a file called routes.js that I am trying to import from both the client and the server. It contains shared imports, as well as some client and server specific ones:

import './shared'

if (Meteor.isServer) { 
  import './server1'
  import './server2'
}

Now using the bundle-visualizer package I am able to see that the imports under Meteor.isServer are included in the client-side bundle. Is this the expected behavior? I also tried using require under the isServer block, but it made no difference.

Edit: From another thread, for anyone else searching:

Shared methods with module import

If you do conditional imports, the code is not executed but it is still shipped to the client.

Didn’t think of it before but if you put the secret code in a “server” folder it won’t be shipped to the client. I didn’t realize “server” folders are honored as server-only in the new “/imports” folder, but they are.

In all the confusion, the correct way is:

Put all secret code in “server” folders. The folders can be located anywhere in the dir tree.
Use if (Meteor.isServer) {import…} to import the modules (the app will anyways not compile if you don’t, since the client would try to import a module that does not exist.

[robfallows]

Is this now resolved for you? (if it is, could you update the title with "[Solved] " - thanks )