Allow transforms to be ignored #945
Conversation
|
Looks good and I'm down with merging this patch, but can you describe your specific use-case a little bit, just so I have a better picture of what kind of scenario this feature is for? |
|
Yep, basically I'm exploring some ways of optimizing bundle size at the application level. Transforms could inline content into the bundle, like urify for base64 images. Or another example might be a transform to inline CSS and inject it with insert-css: require('static-css')(__dirname+'/style.less', { transform: 'less-stream' })In both cases the browserified bundle would work because the transforms are listed, but it wouldn't be ideal for frontend. For images, it would be better to load from a URL with the So the plugin would only be for optimizing the bundle at the application level; overriding all transforms throughout the bundle with some app-specific emitter. An example with images here: If you have other ideas on how to tackle this, I'm all ears. Or maybe static analysis is not the right tool here, and using package.json a la Atomify would be more suitable? |
|
This seems like a reasonable way to achieve the goal, and it's just turning off a feature, not actually adding anything as such. |
ghost
merged commit
|
Merged in 6.1.0. Thanks for the patch! |
This lets you ignore transforms by name, and it trickles down to the module dependency level so they get ignored through the entire bundle. The general idea here is to apply a global top-level transform after the fact, that gets applied to the entire bundle, i.e. to override a transform completely for application-specific purposes.