Skip to content

Support Node.js 18 #17

Closed
Closed
@oliviertassinari

Description

@oliviertassinari

Because we are using Next.js v10, candidates can't use Node.js v18 or later. The current workaround for them is to do:

diff --git a/docs/package.json b/docs/package.json
index 916e7c3..37b07ef 100644
--- a/docs/package.json
+++ b/docs/package.json
@@ -8,7 +8,7 @@
     "build": "cross-env NODE_ENV=production next build --profile",
     "build:clean": "rimraf .next && yarn build",
     "build-sw": "node ./scripts/buildServiceWorker.js",
-    "dev": "rimraf ./node_modules/.cache/babel-loader && next dev --port 3002",
+    "dev": "rimraf ./node_modules/.cache/babel-loader && NODE_OPTIONS=--openssl-legacy-provider next dev --port 3002",
     "deploy": "git push material-ui-docs next:next",
     "export": "rimraf docs/export && next export --threads=3 -o export && yarn build-sw",
     "icons": "rimraf public/static/icons/* && node ./scripts/buildIcons.js",

Going forward, we might have to recreate the whole https://github.com/mui/react-technical-challenge repository using the latest version of http://github.com/mui/material-ui.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementThis is not a bug, nor a new feature

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions