Temp deploy fix [DO NOT MERGE] #499
Open
+12
−11
Conversation
This file contains 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
|
[diff-counting] Significant lines: 5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Implemented the
--openssl-legacy-providerflag in ourstartandbuildscript to address an OpenSSL-related error encountered with newer versions of Node. This change allows our application to bypass theERR_OSSL_EVP_UNSUPPORTEDerror, enabling compatibility with older dependencies that require legacy OpenSSL support.Notes
Encountered a runtime error due to OpenSSL version incompatibility. The issue arises from the stricter default settings for OpenSSL in Node.js v17 and above, affecting older dependencies:
A link to a similar issue with the outdated cryptographic dependency here
Issue