Dynamic import path does not work

[WayneUong]

This works: import('/imports/client/main.js');
This doesn't work: import('/imports/client/' + 'main.js');

[dr-dimitru]

@WayneUong does this produce an error? error stack?

[WayneUong]

I got this error:

modules-runtime.js?hash=8587d18…:231 Uncaught (in promise) Error: Cannot find module '/imports/client/main.js'
    at makeMissingError (modules-runtime.js?hash=8587d18…:231)
    at Function.require.resolve (modules-runtime.js?hash=8587d18…:263)
    at Module.resolve (modules-runtime.js?hash=8587d18…:121)
    at modules-runtime.js?hash=8587d18…:183
    at meteor.js?hash=27829e9…:1105
    at <anonymous>

[benjamn]

This is a deliberate design decision and not a bug: #8327 (comment)

tl;dr If you indicate elsewhere in your client code that the module should be made available (using import(id) where id is a statically analyzable string literal), then any dynamic expression will work in other places. However, the Meteor server will not make modules available for import unless your code expresses the dependency at build time.

[dr-dimitru]

@benjamn it's good to know, we should explicitly mention this in the documentation

[benjamn]

@dr-dimitru good idea!

[hwillson]

Thanks @dr-dimitru - I've created meteor/guide#641 so we don't lose track of this.