Fix Storybook OpenSSL Error on Node.js v17+ by Using Legacy Provider #531
+10
−2
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.
Summary & motivation
Storybook was failing to run on Node.js v17+ due to OpenSSL breaking changes and Webpack's use of deprecated crypto functions. Added the --openssl-legacy-provider flag to the NODE_OPTIONS in the storybook script in package.json. This ensures compatibility with newer Node.js versions without requiring a downgrade.
Testing & documentation
Before making changes
After Making changes...
Storybook runs successfully.