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
{{ message }}
This repository has been archived by the owner on Jun 11, 2023. It is now read-only.
Since you give the option (freedom) for default plugins (CSSPlugin and esbuildPlugin) not to be included (i.e. to get disabled), it may would be better to cancel the term "default" and make both of them select-able as the rest ones. They are not needed to be enabled by default.
Under the same thought, also the term built-in may would be cancelled.
So, you will have by default a fully modular dev environment!
Further, you could adopt categories such as:
Auxiliary
FilePlugin
ReplacePlugin
UsePlugin
etc
CSS
CSSPlugin
LitCSSPlugin
PostCSSPlugin
SassPlugin
etc
Transformers
BabelPlugin
esbuildPlugin
etc
Frameworks
ReactRefreshPlugin
SveltePlugin
VuePlugin
etc
etc
I think it's simpler and more straight. One can choose whatever wants to work with.
The text was updated successfully, but these errors were encountered:
Since you give the option (freedom) for default plugins (
CSSPlugin
andesbuildPlugin
) not to be included (i.e. to get disabled), it may would be better to cancel the term "default" and make both of them select-able as the rest ones. They are not needed to be enabled by default.Under the same thought, also the term
built-in
may would be cancelled.So, you will have by default a fully modular dev environment!
Further, you could adopt categories such as:
I think it's simpler and more straight. One can choose whatever wants to work with.
The text was updated successfully, but these errors were encountered: