browserify / browserify/browserify

plugins and their scope

Open
#944 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
14.7k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Not much info is written on plugins right now. It seems like they are intended to be used only at the application-level, and for things like emitting multiple files (factor-bundle being a good example).

But they don't have "full control" over the bundler like you may need for an application-specific plugin. For example, to override or disable transforms across module dependencies.

Shouldn't the plugins be the first thing that are instantiated on the bundler, rather than the last? And, further, shouldn't the plugin features also trickle down to the dependencies handled by module-deps? Or am I misunderstanding the goal of these plugins?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.