FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

browserify production/development/staging/testing/etc... flags to change the set of applied transforms · Issue #1715 · browserify/browserify · GitHub

browserify production/development/staging/testing/etc... flags to change the set of applied transforms #1715

Description

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL