You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm glad this fixed someone's workflow, but it broke mine 😄.
We run browserify but target Node.js (browserify is useful to generate single JS files). This change means we now get a Cannot find module 'babelify' from '/node_modules/async' error. We can work around that by adding ignoreTransform: ['babelify'] though.
In general, I think this change means that anyone running browserify over async will need to either add babelify as a dependency or take steps to ignore the transform.
What are you thinking? Why do I need to add "babelify" "@babel/core" and "@babel/preset-env" to my project. I do not want to use babel. I just want to bundle my dependencies.
Even if I would use a transpiler, this whole concept does not work with devDependencies. Why should every library provide its own rollup/webpack/browserify config and then require downstream to include their dev dependencies manually?
Also now that I am doing that, I am not able to change the configuration. For example how am I supposed to manage polyfills (regenerator-runtime in this case), if I cannot even change the @babel/preset-env configuration (for example to "usage"), or the target?
This is madness. I will just stick with v2. Thanks. Babelify my ass. (humour)
A more resonable approach would be to target a specific node version, and if you want to use newer features in your source, then transpile it yourself prior to publishing to npm, or just leave them in and leave it to downstream how they want to transpile it for their environment as necessary.
This approach (sorry if I repeat mysdelf) is complete nonsense.