Presets - Add "addons" and "config" to preset extensions #4240
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've played a bit with presets and realized that having more granular extensions for
addons
andconfig
will be very helpful for creating presets.For example, we can expose our addons as presets, i.e. using them like this:
Same thing with a
config.js
file. Today we enforce people to createconfig.js
in order to call theconfigure(loadStories, module);
We can create a preset that does it. One may use
require.context
or some other techniques.