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.

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

Jump to bottom

Upgrade to using latest version of NodeJS #332

Open
Michaelpalacce opened this issue Jul 15, 2024 · 2 comments
Open

Upgrade to using latest version of NodeJS #332

Michaelpalacce opened this issue Jul 15, 2024 · 2 comments
Labels
area/build Relates to the build process area/vro-scripting-api Relates to the vro-scripting-api module area/vropkg Relates to `vropkg` module dependencies Pull requests that update a dependency file effort/medium kind/enhancement Enhancement or improvement of existing features priority/medium triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change

Comments

@Michaelpalacce
Copy link
Collaborator

Michaelpalacce commented Jul 15, 2024 •
edited
Loading

Description

Target is to be using the newest possible version of NodeJS as long as it's not too hard to do so. Target is Node 20, but newer LTS versions are also good.

One major problem is building vcd projects as that requires an outdated version of Angular, enforcing Node 14... However newer versions of vcd actually have a newer version of angular that works with newer versions of node just fine.

The proposition here is in the case of vcd, we can drop support for versions requiring the outdated version of Angular.
@Michaelpalacce Michaelpalacce added kind/enhancement Enhancement or improvement of existing features area/build Relates to the build process triage/needed Needs to be discussed by project maintainers labels Jul 15, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Aug 15, 2024
@Michaelpalacce Michaelpalacce added triage/accepted The issue was accepted and will be done and removed Stale triage/needed Needs to be discussed by project maintainers labels Aug 15, 2024
@Michaelpalacce Michaelpalacce mentioned this issue Sep 18, 2024
Closed
@VenelinBakalov
Copy link
Collaborator

Additional request related to this issue:

  • update @type/node dependencies to at least ^14.0.13 and make the dependency consistent across the whole project
    ** vrotsc uses: ^14.0.0
    ** vropkg uses: ^11.15.7
    ** npmconv uses: ^12.0.10
  • research the possibility of using PNpm

Suggested by @Indy-rbo in #401

@VenelinBakalov VenelinBakalov added area/vro-scripting-api Relates to the vro-scripting-api module area/vropkg Relates to `vropkg` module version/minor Introduces a non-breaking feature or change effort/medium dependencies Pull requests that update a dependency file priority/medium labels Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/build Relates to the build process area/vro-scripting-api Relates to the vro-scripting-api module area/vropkg Relates to `vropkg` module dependencies Pull requests that update a dependency file effort/medium kind/enhancement Enhancement or improvement of existing features priority/medium triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Michaelpalacce @VenelinBakalov