Fix OpenSSL compatibility issue in Node.js#36
Open
arnavbee wants to merge 1 commit into
Open
Conversation
❌ Deploy Preview for eth2book failed.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description (#35 )
To run the project successfully, clone the repository and setup locally.
Run this command in the bash:
export NODE_OPTIONS=--openssl-legacy-providerthen run
npm run devThis PR addresses the compatibility issue encountered with Node.js version 17 and higher, which leads to errors related to OpenSSL 3.0. The following changes have been made:
Downgraded Node.js: Updated the project to use Node.js version 16.x to ensure compatibility and prevent the error: error:0308010C:digital envelope routines::unsupported.
Environment Variable Option: Added instructions to set the NODE_OPTIONS environment variable to allow legacy OpenSSL providers as an alternative solution.
Changes Made
Testing
Verified that the project runs successfully with Node.js version 16.x.
Confirmed that setting the NODE_OPTIONS environment variable resolves the issue for those who prefer to use a higher Node.js version.