Unable to Run Node.js Website Locally on Windows 11 with Node.js 18.18.0 and npm 9.8.1 #5921

shaikahmadnawaz · 2023-09-30T03:17:39Z

URL:

https://github.com/nodejs/nodejs.org

Browser Name:

Brave

Browser Version:

v1.58.135

Operating System:

Windows 11, 22H2, 22621.2283

How to reproduce the issue:

Problem: I am encountering difficulties when trying to run the Node.js Website locally on my Windows 11 machine using Node.js version 18.18.0 and npm version 9.8.1. The local development environment is not working as expected.

Steps to Reproduce:

Clone the Node.js Website repository.
Run npm ci to install project dependencies.
Attempt to start the local preview with npx turbo serve.

Expected Behavior: The local development environment should start without errors, allowing me to preview my changes.

Actual Behavior:

npm ci

npx turbo serve

Environment:

Operating System: Windows 11
Node.js Version: 18.18.0
npm Version: 9.8.1

The text was updated successfully, but these errors were encountered:

shaikahmadnawaz · 2023-09-30T09:09:21Z

have you try to use npm I ? it's can change something 🤔

I tried that too.

shaikahmadnawaz · 2023-09-30T09:28:16Z

have you try to use npm I ? it's can change something 🤔

Check this once @AugustinMauroy

shaikahmadnawaz · 2023-09-30T10:28:37Z

could you try to remove node_modules and after npm i ?

Still facing the same error 🥲, please help.

AugustinMauroy · 2023-09-30T10:35:27Z

apart from the error message during installation, what happens when you run the project ?

shaikahmadnawaz · 2023-09-30T10:38:10Z

apart from the error message during installation, what happens when you run the project ?

shaikahmadnawaz · 2023-09-30T10:44:03Z

what is the change do in your branch ?

These are automatically generated when I try to install and run it.

ovflowd · 2023-09-30T11:15:40Z

what is the change do in your branch ?

These are automatically generated when I try to install and run it.

The changes on package-lock should not be done. The files on public are generated automatically and that's fine. The changes on the VS Code settings are due to you probably altering it. Either by accepting/rejecting a VS Code prompt.

ovflowd · 2023-09-30T11:16:32Z

have you try to use npm I ? it's can change something 🤔

Check this once @AugustinMauroy

This is fine. We manually disable Next.js telemtry.

shaikahmadnawaz · 2023-09-30T11:21:55Z

Okay then, any solution for this? to stop the change in package-lock.json @ovflowd

ovflowd · 2023-09-30T11:22:36Z

It's important to mention that react is a peer dependency (https://github.com/nodejs/nodejs.org/blob/main/package.json) and since NPM v7 they are automatically installed.

Something is wrong on your Node.js setup. That's the only I thing I can think of. Do you use WSL or anything? How did you install Node.js?

ovflowd · 2023-09-30T11:22:54Z

I've made a fresh clone here, on my Windows machine. Everything is working fine.

ovflowd · 2023-09-30T11:24:46Z

My recommendation:

Reinstall Git, and use Git Bash if possible
Reinstall Node.js and check the mark of "install additional node.js dev tools" when using the Node.js installer. Download the latest LTS.
Delete the nodejs.org folder after all of this and reclone the repository
Disable/Remove VSCode Extensions. We recommend only using the ones recommended by the repository (.vscode/extensions.json)
- Sometimes other extensions play and mess around with things

ovflowd · 2023-09-30T11:25:47Z

Also, regarding these two files, simply read the Collaborator Guidelines. These are autogenerated files, and they always generate automatically. It's fine keeping them and they never commit by themselves. We have a Git Hook that automatically ignores these files on commits.

shaikahmadnawaz · 2023-09-30T13:35:05Z

It's important to mention that react is a peer dependency (https://github.com/nodejs/nodejs.org/blob/main/package.json) and since NPM v7 they are automatically installed.

Something is wrong on your Node.js setup. That's the only I thing I can think of. Do you use WSL or anything? How did you install Node.js?

I used NVM to install nodejs 18.18.0

shaikahmadnawaz · 2023-09-30T13:36:15Z

My recommendation:

Reinstall Git, and use Git Bash if possible

Reinstall Node.js and check the mark of "install additional node.js dev tools" when using the Node.js installer. Download the latest LTS.

Delete the nodejs.org folder after all of this and reclone the repository

Disable/Remove VSCode Extensions. We recommend only using the ones recommended by the repository (.vscode/extensions.json)

Sometimes other extensions play and mess around with things

Sure, I will do all these steps.

shaikahmadnawaz · 2023-09-30T13:36:31Z

Also, regarding these two files, simply read the Collaborator Guidelines. These are autogenerated files, and they always generate automatically. It's fine keeping them and they never commit by themselves. We have a Git Hook that automatically ignores these files on commits.

Okay

shaikahmadnawaz · 2023-09-30T13:43:41Z

I've made a fresh clone here, on my Windows machine. Everything is working fine.

Thank you so much for making these many efforts for me @ovflowd

ovflowd · 2023-09-30T13:46:41Z

No worries. Hopefully you figure out what's wrong

shaikahmadnawaz · 2023-09-30T13:48:45Z

No worries. Hopefully you figure out what's wrong

Yes, working on the steps you mentioned, will update you if I figure it out. 👍

shaikahmadnawaz · 2023-09-30T14:12:55Z

It's not working 🥲 @ovflowd

shaikahmadnawaz · 2023-09-30T14:14:40Z

It's okay leave, I am using GitHub codespace to run it locally, see @ovflowd this is how it looks ✨

ovflowd · 2023-09-30T14:15:08Z

Do you have Git Bash installed?

Can you run ls -la within node_modules with Git Bash?

How are you installing packages?

Are you still using NVM? Have you installed node with Node MSI installer and added the additional tools?

ovflowd · 2023-09-30T14:16:06Z

It's okay leave, I am using GitHub codespace to run it locally, see @ovflowd this is how it looks ✨

Codespaces saves the day, but Id still love to get to the bottom of it 😅

As Im genuinely curious what could be causing this 🫠

shaikahmadnawaz · 2023-09-30T14:20:05Z

Do you have Git Bash installed?

Can you run ls -la within node_modules with Git Bash?

How are you installing packages?

Are you still using NVM? Have you installed node with Node MSI installer and added the additional tools?

git did, Yes, I installed node with Node MSI installer and added the additional tools, yes I can run ls -la within node_modules with Git Bash, I am Installing packages using git bash and the command is npm ci

ovflowd · 2023-09-30T14:21:28Z

Do you have Git Bash installed?

Can you run ls -la within node_modules with Git Bash?

How are you installing packages?

Are you still using NVM? Have you installed node with Node MSI installer and added the additional tools?

git did, Yes, I installed node with Node MSI installer and added the additional tools, yes I can run ls -la within node_modules with Git Bash, I am Installing packages using git bash and the command is npm ci

Gotcha, what I meant to ask is if with ls -la you see the react folder inside node_modules

I want to understand if somehow npm decided to not install the peerDependency

ovflowd · 2023-09-30T14:25:18Z

I mean can you run

cd node_modules && ls -la

Also last question, do you have a .npmrc on your machine?

cat ~/.npmrc

shaikahmadnawaz · 2023-09-30T14:26:10Z

I mean can you run

cd node_modules && ls -la

Also last question, do you have a .npmrc on your machine?
cat ~/.npmrc

shaikahmadnawaz · 2023-09-30T14:27:04Z

cat ~/.npmrc

$ cat ~/.npmrc
legacy-peer-deps=true

ovflowd · 2023-09-30T14:27:44Z

cat ~/.npmrc

$ cat ~/.npmrc
legacy-peer-deps=true

We found the issue. can you delete that file? And then delete node_modules of your repository and run npm i again. That should do the trick...

shaikahmadnawaz · 2023-09-30T14:30:34Z

cat ~/.npmrc
$ cat ~/.npmrc
legacy-peer-deps=true
We found the issue. can you delete that file? And then delete node_modules of your repository and run npm i again. That should do the trick...

Yes, doing

shaikahmadnawaz · 2023-09-30T14:31:09Z

ovflowd · 2023-09-30T14:31:45Z

Yeah seems alright now, feel free to try npx turbo serve

shaikahmadnawaz · 2023-09-30T14:33:12Z

Here we go, now it's working absolutely fine ✨

ovflowd · 2023-09-30T14:33:50Z

Glad to hear issue was solved ;)

shaikahmadnawaz · 2023-09-30T14:35:28Z

Thank you so much for guiding me, and hats off to your patience @ovflowd 👏

ovflowd · 2023-09-30T14:38:50Z

Thank you so much for guiding me, and hats off to your patience @ovflowd 👏

Of course :) Here to help!

shaikahmadnawaz · 2023-09-30T14:41:23Z

One final query, what does .npmrc file do or why it is added or removed? @ovflowd

ovflowd · 2023-09-30T14:50:10Z

One final query, what does .npmrc file do or why it is added or removed? @ovflowd

.npmrc is a NPM configuration file that allows you to override default NPM settings. The issue that comes from that specific issue, is that since NPM v7, peerDependencies (which react is one) are installed automatically alongside regular dependencies.

With the legacy-peer-deps they won't. Hence why react did not get installed.

More details: npm/cli#4934

shaikahmadnawaz added the bug label Sep 30, 2023

shaikahmadnawaz mentioned this issue Sep 30, 2023

Create NavItem Component #5911

Closed

This comment was marked as off-topic.

Sign in to view

This comment has been minimized.

Sign in to view

ovflowd closed this as completed Sep 30, 2023

ovflowd mentioned this issue Sep 30, 2023

fix: some npm settings tweaks #5923

Merged

Unable to Run Node.js Website Locally on Windows 11 with Node.js 18.18.0 and npm 9.8.1 #5921

Unable to Run Node.js Website Locally on Windows 11 with Node.js 18.18.0 and npm 9.8.1 #5921

Comments

shaikahmadnawaz commented Sep 30, 2023 • edited Loading

URL:

Browser Name:

Browser Version:

Operating System:

How to reproduce the issue:

This comment was marked as off-topic.

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

This comment was marked as off-topic.

shaikahmadnawaz commented Sep 30, 2023

AugustinMauroy commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

This comment was marked as off-topic.

shaikahmadnawaz commented Sep 30, 2023

This comment was marked as off-topic.

ovflowd commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

ovflowd commented Sep 30, 2023

ovflowd commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

This comment has been minimized.

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023 • edited Loading

shaikahmadnawaz commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023

ovflowd commented Sep 30, 2023

shaikahmadnawaz commented Sep 30, 2023 •

edited

Loading

ovflowd commented Sep 30, 2023 •

edited

Loading