support for vendor prefixed nwb plugins #438
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to add support for vendor prefixed plugins with the idea being that I can essentially create a plugin or I guess more accurately it would be a preset for my company. So for example, I would add
@mycompany/nwb-react-component
to my dependencies which in turn would include thenwb-less
and ideally any other webpack config changes I use at my company. So the main entry for the@mycompany/nwb-react-component
would look something like this...Looking at the code it looks like the plugins currently have very limited effect on the build, so currently it looks like really I'll just be able to hook the
nwb-less
plugin there and thats about it. So i'll be looking into making some changes there to support setting up other things. For example, at my company we'd prefer to use.jsx
file extensions, so we'll want to be able to add that to the list if extensions handled by the webpack babel plugin.