Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
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 docs/.nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.18.3
v22.22.0
2 changes: 1 addition & 1 deletion superset-embedded-sdk/.nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.18.3
v22.22.0
2 changes: 1 addition & 1 deletion superset-frontend/.nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.18.3
v22.22.0
2 changes: 1 addition & 1 deletion superset-frontend/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion superset-frontend/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -375,7 +375,7 @@
"regenerator-runtime": "^0.14.1"
},
"engines": {
"node": "^20.18.1",
"node": "^22.22.0",
"npm": "^10.8.1"
},
"overrides": {
Expand Down
2 changes: 1 addition & 1 deletion superset-websocket/.nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.18.3
v22.22.0

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Version Mismatch

The .nvmrc specifies Node.js v22.22.0, but the package.json engines require '^20.19.4', creating an inconsistency that could cause issues with package managers or CI if engines are enforced.

Code Review Run #aa8f23


Should Bito avoid suggestions like this for future reviews? (Manage Rules)

  • Yes, avoid them

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@hainenber I do remember having to update this in a few random places last time I did it (a long time ago!)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wonder if there's some good way to centralize all of this to make it easier.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, to centralize Node.js version management in this monorepo, consider placing a single .nvmrc at the root. This lets all subprojects inherit the version. Alternatively, use Volta by adding a 'volta' field in the root package.json specifying the node version.

.nvmrc

v22.22.0

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We can have a centralized .nvmrc in root dir /superset and sym-link this particular file to other sub-projects. Wdyt?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Centralizing the .nvmrc at the root and sym-linking to sub-projects is a solid idea—it reduces duplication and simplifies updates across the monorepo. Just ensure sym-links are handled properly in CI/CD and version control to avoid issues.

2 changes: 1 addition & 1 deletion superset-websocket/utils/client-ws-app/.nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.18.3
v22.22.0
Loading