Skip to content

docs: change node and npm version in Development.md to a compatible version #1457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Apr 23, 2025
+1 −1
Merged

docs: change node and npm version in Development.md to a compatible version #1457

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5ff4034
Changed minimum Node and NPM version in Development.md to a version t…
pseudo-tensor Mar 29, 2025
b51eac8
Merge branch 'master' into fix-node-ver-in-devdocs
pseudo-tensor Apr 3, 2025
dde53e1
Merge branch 'master' into fix-node-ver-in-devdocs
pseudo-tensor Apr 3, 2025
1e5ffd5
Merge branch 'master' into fix-node-ver-in-devdocs
pseudo-tensor Apr 5, 2025
03cc3aa
Merge branch 'master' into fix-node-ver-in-devdocs
pseudo-tensor Apr 17, 2025
0bf548c
Merge branch 'master' into fix-node-ver-in-devdocs
derberg Apr 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Development.md
View file
Original file line number Diff line number Diff line change
@@ -177,7 +177,7 @@ For the PR titles you can refer to [this guide](CONTRIBUTING.md?plain=1#L60)

If you encounter any issues during development or testing, please check the following:

1. Ensure you're using the correct Node.js version (18.12.0 or higher) and npm version (8.19.0 or higher).
1. Ensure you're using the correct Node.js version (18.20.8 or higher) and npm version (10.8.2 or higher).
Copy link
Member

Choose a reason for hiding this comment

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

why 18.20.8?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it's the node version being used in the docker image in the repo so that way there will be consistency in the node version in local setup and in the docker container

2. Clear the `node_modules` directory and reinstall dependencies if you encounter unexpected behavior.
3. For Docker-related issues, make sure Docker is running and you have sufficient permissions.