Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Does not work on Node 16 which is dynamically linked to openssl 3
See original GitHub issueDescription of the bug
If you have a new Node 16 installed that is dynamically linked to openssl3, building the frontend fails with
'/usr/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
Expected behavior
You can use a Node 16 version dynamically linked with openssl3
Minimal reproducible example
Versions
- Vaadin / Flow version: 23.1.rc1
Issue Analytics
- State:
- Created a year ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Fix Node.js OpenSSL issues on Heroku-22
This issue arises from Node.js versions 16 and older statically linking against OpenSSL version 1, running on a system that uses OpenSSL version...
Read more >Bug #1979639 “Apps expecting an OpenSSL 1.1 -formatted ...
I'll reject the openssl upload from Jammy, and mark that task Won't Fix. We won't update the default configuration in Jammy. Third parties...
Read more >node: --openssl-legacy-provide is not allowed in node_options
Firstly I'm using this command export NODE_OPTIONS=--openssl-legacy-provider before any command in GitBash Windows to fix this issue.
Read more >Can node-gyp extension call extension linked OpenSSL ...
I have a library that calls the openssl 1.0 API. I can either dynamically link or statically link. Either produces the same result....
Read more >Bringing forward the End-of-Life Date for Node.js 16
Attempt a switch to OpenSSL 3. Based on issues reported against Node.js 17 and 18 (which are on OpenSSL 3) and adjustments that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Assuming it works
Flow 9.0 snapshot validation in Bender failed when I added
NODE_OPTIONS=--openssl-legacy-providerenv variable to the build (it was added to fix flow-client tests, now flow-client fixed in another way). But I got some explanations here https://github.com/nodejs/node/pull/40478#issuecomment-1253490805, so this parameter is not needed when open ssl 1.1.1 is used (by default).