Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundles don't work anymore in Meteor 1.8.2 #9

Open
fknipp opened this issue Nov 15, 2019 · 1 comment
Open

Bundles don't work anymore in Meteor 1.8.2 #9

fknipp opened this issue Nov 15, 2019 · 1 comment

Comments

@fknipp
Copy link

fknipp commented Nov 15, 2019

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: meteor/meteor#10780

@fknipp
Copy link
Author

fknipp commented Dec 6, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant