WRP-11048: Move storybook-related modules from devDependencies to dependencies #745
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.
Checklist
Issue Resolved / Feature Added
When you initialize a storybook, the module related to the storybook is automatically installed in devDependencies.
(https://storybook.js.org/docs/react/get-started/install , in simply, $ npx storybook@latest init)
There was no reason to be managed as devDependencies even if you checked related documents or developer sites, and it is right to move to dependencies because the sampler directory itself aims to create samplers through storybooks.
Resolution
Move storybook-related modules from devDependencies to dependencies
Additional Considerations
Removed the
core-js
module.The
core-js
module is not needed. I cannot find any code usage and the sampler works fine without this module.Links
WRP-11048
Comments
Enact-DCO-1.0-Signed-off-by: Taeyoung Hong (taeyoung.hong@lge.com)