This repository was archived by the owner on Mar 5, 2025. It is now read-only.
Move browserify transforms to package.json #87
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
|
I'm happy to provide further explanation, just ask |
|
@debris if there is anything I can do to help get this merged, let me know 😸 |
|
looks good! thanks! |
debris
added a commit
that referenced
this pull request
Feb 28, 2015
Move browserify transforms to package.json
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Browserify will automatically read the
package.jsonand run the transforms. This produces the exact same build as specifying the transforms in thegulpfile.js. Additionally, now when someone tries to externally browserifyethereum.js, it will use the same transforms as when you usegulp. Yay! Consistency!Fixes #86
Fixes #36