Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove browserify-pipe #2183

Merged
merged 1 commit into from Apr 30, 2015
Merged

Remove browserify-pipe #2183

merged 1 commit into from Apr 30, 2015

Conversation

tilgovi
Copy link
Contributor

@tilgovi tilgovi commented Apr 19, 2015

This is totally safe unless there is another input filter before
browserify, but let's just say that's not allowed because it
simplifies things nicely to not have this extra script.

@tilgovi
Copy link
Contributor Author

tilgovi commented Apr 19, 2015

For @nickstenning

This is totally safe unless there is another input filter before
browserify, but let's just say that's not allowed because it
simplifies things nicely to not have this extra script.
@tilgovi
Copy link
Contributor Author

tilgovi commented Apr 30, 2015

I'm going with this. As an input filter, browserify should be acting on each file independently. The only issue would be if another filter was wrapped inside browserify.

I think that's got to be considered incorrect usage. If you need to filter things at that point, the browserify transform stack is the place to do it.

tilgovi added a commit that referenced this pull request Apr 30, 2015
@tilgovi tilgovi merged commit 777b66b into master Apr 30, 2015
@tilgovi tilgovi deleted the vanilla-browserify branch April 30, 2015 19:06
@nickstenning
Copy link
Contributor

Retroactive 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants