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 using tsify to compile TypeScript input to browserify. tsify exists as a plugin, since it uses the TypeScript compiler for dependency resolution. Because it does this, tsify must be registered with Browserify before any transforms. Unfortunately for me, Browserify runs all transforms before plugins!
My solution right now is to add a configure callback to manually invoke the API, but I wanted to open this issue to see if it would be a good idea to change grunt-browserify's behavior to register plugins before transforms. I'm relatively new to the Browserify ecosystem, so I don't know if the converse is ever true -- e.g. that a transform must be registered before all plugins. If it's not, then this behavior change would be benign. 😄
The text was updated successfully, but these errors were encountered:
jvilk
changed the title
Run plugins *before* transforms?
Register plugins *before* transforms?
Oct 23, 2015
I'm using tsify to compile TypeScript input to browserify. tsify exists as a plugin, since it uses the TypeScript compiler for dependency resolution. Because it does this, tsify must be registered with Browserify before any transforms. Unfortunately for me, Browserify runs all transforms before plugins!
My solution right now is to add a
configure
callback to manually invoke the API, but I wanted to open this issue to see if it would be a good idea to change grunt-browserify's behavior to register plugins before transforms. I'm relatively new to the Browserify ecosystem, so I don't know if the converse is ever true -- e.g. that a transform must be registered before all plugins. If it's not, then this behavior change would be benign. 😄The text was updated successfully, but these errors were encountered: