Morten N.O. Nørgaard Henriksen

Investigating if webpack config of mainfields is the root cause of the issue https://webpack.js.org/configuration/resolve/#resolvemainfields

Opened an issue in Webpack: https://github.com/webpack/webpack/issues/15007 If a package like "handlebars" is imported, webpack fails to resolve import using the existing "browser" main field and fallsback to using the "main"...

@Rubenvet please use the issue tracker or stack overflow - this pull-request is for discussing a solution

I see the intent of the Webpack resolve.fallback option a tool for package maintainers - not consumers of packages

Suggestion for documentation / migration: https://github.com/facebook/create-react-app/issues/11756#issuecomment-996464456

This PR set nodejs builin fallbacks to `false` in production and a debug fallback in development with error message and link to documentation if any code is using the module...

@aldeed Should it work on eg. `Template.foo.helpers({});` or/and global helpers? ``` {{bar name=""}} Set in "Template.foo" scope ``` - It should know if its a global helper or scoped -...

it depends on your code - it's using regular meteor stuff - so it should be pr. client connection - but the code calling emit have to be aware

good question - try wrapping the emit in a `Meteor.defer` or maybe in a `setTimeout(()=>{}, 0)` _(there might be an issue with connection context)_

True - but being on the "lazy" side I've just linked to the node api docs - it should work the same (thats the intend) :)