Open iMnoorfahad opened 5 months ago
This update introduces a modification to the start
and build
scripts in the package.json
by appending the --openssl-legacy-provider
flag to the craco
command. This adjustment aims to address issues related to OpenSSL errors during the project's initialization and build processes.
File | Change Summary |
---|---|
package.json |
Added --openssl-legacy-provider to start and build scripts |
ERR_OSSL_EVP_UNSUPPORTED
errors which are directly addressed by the inclusion of the --openssl-legacy-provider
flag in this PR. This change should help in resolving the OpenSSL related initialization error described.🐰✨ A little flag in scripts so neat, Helps OpenSSL not admit defeat. With
craco
now gently tweaked, No more errors shall be leaked. Hop, hop, hurray, let's start the feat! 🚀 🐰✨
package.json (1)
`71-72`: The inclusion of `--openssl-legacy-provider` in both `start` and `build` scripts is a suitable workaround for the OpenSSL error. Ensure that all environments where the project will be built or run support this flag.
Description
This pull request addresses the issue related to the OpenSSL error stack, specifically:
The problem has been resolved by adding the
--openssl-legacy-provider
flag in the start script as follows:This change fixes the issue # (replace with the relevant issue number).
Type of change
How Has This Been Tested?
I have tested this change locally by running the updated start script with the
--openssl-legacy-provider
flag. The application started without encountering the OpenSSL error mentioned above.To test this change:
yarn install
.yarn start
.Checklist:
Summary by CodeRabbit