Skip to content

Conversation

@mt-dfrey
Copy link
Contributor

@mt-dfrey mt-dfrey commented Oct 5, 2023

  • build(all) upgrade node from 12 -> 16
  • build(all) upgrade node from 16 -> 18

@mt-dfrey mt-dfrey requested a review from a team as a code owner October 5, 2023 03:15
"license": "MIT",
"scripts": {
"build": "rm -rf dist && webpack",
"build": "rm -rf dist && NODE_OPTIONS=--openssl-legacy-provider webpack",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see the commit message of 60fbf99 for an explanation of this option.

node 17 switched to openssl 3, which has some incompatibilities with
older versions, see https://nodejs.org/en/blog/release/v17.0.0#openssl-3-0

webpack 4 relies on the older openssl version, only webpack 5 and newer
uses openssl 3, see
webpack/webpack#14532 (comment)
webpack/webpack#14584

That's why we use the --openssl-legacy-provider node option when running
webpack.
@mt-dfrey mt-dfrey merged commit a66a0c1 into master Oct 5, 2023
@mt-dfrey mt-dfrey deleted the upgrade-node branch October 5, 2023 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants