Open fknipp opened 4 years ago
Using static assets from NPM packages works well with symbolic links, as explained in https://guide.meteor.com/using-npm-packages.html#npm-assets
Therefore, I've changed my application to do it as explained in the guide and removed this package.
When using nathantreid:static-assets, Meteor behaves fine in the development mode using meteor run.
During rollout into production a bundle is generated using meteor build direct from the repository clone. Opening the new application in the browser will throw a JavaScript error Uncaught Error: Cannot find module '…'
When generating the bundle a second time without modification of any of the files, it works. No JavaScript errors are shown in the browser.
See https://github.com/qnipp/meteor-double-build-bug to reproduce the bug.
The bug was observed on Linux, using Meteor 1.8.1 and Node version 8.15.1 (which is the corresponding Node version for this Meteor version).
On 1.8.2 and 1.9-beta.3, even a second build does not help, the error remains.
The bug is reported to Meteor as well: https://github.com/meteor/meteor/issues/10780