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
Thinking about CSS preprocessors, It would be nice if you could just install an nwb-sass, nwb-less etc. package which would hook these up with default pipelines for static and server builds like CSS currently has. So a bit of package.json scanning for those.
All they really need to provide is a unique name and test and loader config (absolute path to a dependency owned by the plugin). What if this was the entire nwb-sass plugin?
How much magic do we really want here?
Thinking about CSS preprocessors, It would be nice if you could just install an
nwb-sass
,nwb-less
etc. package which would hook these up with default pipelines for static and server builds like CSS currently has. So a bit ofpackage.json
scanning for those.All they really need to provide is a unique name and
test
andloader
config (absolute path to a dependency owned by the plugin). What if this was the entirenwb-sass
plugin?We could potentially use whatever hook we add for this to allow the user to configure and manage their own preprocessor dependencies.
The text was updated successfully, but these errors were encountered: