Skip to content
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.

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

fix(superset-frontend): resolve installation step problem by using node > 18 #28095

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

corocoto
Copy link
Contributor

@corocoto corocoto commented Apr 16, 2024

SUMMARY

Sets a logical expression "node": ">= 18" at the engines field. It will save backward compatibility with the v18 and allow to work with the frontend part by using newer versions.

ADDITIONAL INFORMATION

Fixes #28094

@corocoto corocoto changed the title fix(superset-frontend): resolve installation step problem by using node v20 fix(superset-frontend): resolve installation step problem by using node > 18 Apr 16, 2024
@@ -353,7 +353,7 @@
"xdm": "^3.4.0"
},
"engines": {
"node": "^18.19.1",
"node": ">= 18",
Copy link
Member

Choose a reason for hiding this comment

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

Should there maybe be an upper bound and/or have a mechanism to exclude odd (non-even) versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@john-bodley, we can set the range of available versions. As example:

{
  "engines": {
    "node": ">=18 <21"
  }
}

NB. For more info you can read the section about engines field from the official npm docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't install superset-frontend dependencies by using node v20.11.1 and yarn v1.22.22
2 participants