This pull request enabled the usage from the cli.
#1709
I just figured out, that when I use:
- browserify --transform-key=production index.js > bundle.js
Then browserify will also use that production key for all the dependencies.
Most dependencies, if they have a "browserify" field in package.json only specify "transform" property and not a "production" property, so browserify often fails when the custom --transform-key feature is used.
How to deal with this?
- Would it be "smart" to automatically fall back to the "transform" key if for example in the above example a "production" key is specified?
Reactions are currently unavailable
This pull request enabled the usage from the cli.
#1709
I just figured out, that when I use:
Then browserify will also use that production key for all the dependencies.
Most dependencies, if they have a "browserify" field in package.json only specify "transform" property and not a "production" property, so browserify often fails when the custom --transform-key feature is used.
How to deal with this?