Closed arnaudbzn closed 3 years ago
Didn't your npm install step fail because it didn't explicitly detect node 14? It did for me, and that made me upgrade node.
I'm using nvm. No issue during the install in v12:
fsevents@1.2.13 install /Users/Arnaud/Dev/Reactive/server-components-demo/node_modules/watchpack-chokidar2/node_modules/fsevents
> node install.js
SOLINK_MODULE(target) Release/.node
CXX(target) Release/obj.target/fse/fsevents.o
SOLINK_MODULE(target) Release/fse.node
> nodemon@2.0.6 postinstall /Users/Arnaud/Dev/Reactive/server-components-demo/node_modules/nodemon
> node bin/postinstall || exit 0
added 939 packages from 431 contributors and audited 941 packages in 11.492s
Thanks, we've added a note to instructions.
With Node v12, I get the error "Error: Cannot find module 'fs/promises'" With Node v13, the server is not running, "node: bad option: --conditions=react-server" in the logs.
Fixed with Node v14.