$ NODE_OPTIONS=--openssl-legacy-provider yarn build
➤ YN0000: [@chainsafe/filsnap-adapter]: Process started
➤ YN0000: [@chainsafe/filsnap]: Process started
➤ YN0000: [@chainsafe/filsnap-adapter]: Process exited (exit code 0), completed in 4s 315ms
➤ YN0000: [@chainsafe/filsnap]: Build success: 'src/index.ts' bundled as 'dist/bundle.js'!
➤ YN0000: [@chainsafe/filsnap]: Manifest Success: Validated snap.manifest.json!
➤ YN0000: [@chainsafe/filsnap]: Eval Success: evaluated 'dist/bundle.js' in SES!
➤ YN0000: [@chainsafe/filsnap]: Process exited (exit code 0), completed in 11s 883ms
➤ YN0000: [example]: Process started
➤ YN0000: [example]: Creating an optimized production build...
➤ YN0000: [example]: Compiled successfully.
➤ YN0000: [example]:
➤ YN0000: [example]: File sizes after gzip:
➤ YN0000: [example]:
➤ YN0000: [example]: 131.99 KB build/static/js/2.324c3289.chunk.js
➤ YN0000: [example]: 6.95 KB build/static/js/main.08f8950d.chunk.js
➤ YN0000: [example]: 770 B build/static/js/runtime-main.65dced8a.js
➤ YN0000: [example]: 72 B build/static/css/main.afd7172b.chunk.css
➤ YN0000: [example]:
➤ YN0000: [example]: The project was built assuming it is hosted at /.
➤ YN0000: [example]: You can control this with the homepage field in your package.json.
➤ YN0000: [example]:
➤ YN0000: [example]: The build folder is ready to be deployed.
➤ YN0000: [example]: You may serve it with a static server:
➤ YN0000: [example]:
➤ YN0000: [example]: npm install -g serve
➤ YN0000: [example]: serve -s build
➤ YN0000: [example]:
➤ YN0000: [example]: Find out more about deployment here:
➤ YN0000: [example]:
➤ YN0000: [example]: https://cra.link/deployment
➤ YN0000: [example]:
➤ YN0000: [example]: Process exited (exit code 0), completed in 19s 684ms
➤ YN0000: Done in 31s 585ms
Should this workaround (NODE_OPTIONS=--openssl-legacy-provider) really be required, or can this fixed?
I am trying to build this project to fix https://github.com/ChainSafe/filsnap/issues/258, but:
https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported
Should this workaround (
NODE_OPTIONS=--openssl-legacy-provider
) really be required, or can this fixed?