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

Enabler: Update Node to supported LTS #19

Open
blairlearn opened this issue Feb 29, 2024 · 0 comments · May be fixed by #21
Open

Enabler: Update Node to supported LTS #19

blairlearn opened this issue Feb 29, 2024 · 0 comments · May be fixed by #21

Comments

@blairlearn
Copy link
Contributor

Update Node JS to a supported LTS version.

We're still on lts/gallium (node 16) which is EOL.
The current LTS version is lts/iron (node 20).

Things to update

  • .nvmrc
  • engines property in package.json (node and npm versions).

ESTIMATE TBD

Prerequisites

Sub-Tasks

Notes

Node release schedule
blairlearn added a commit that referenced this issue Mar 1, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
246c416 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Correct repository urls and package name.
blairlearn added a commit that referenced this issue Mar 1, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
0094021 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Remove comments from configuration files.
  - Config package no longer tolerates them.
- Correct repository urls and package name.

Closes #19
@blairlearn blairlearn linked a pull request Mar 6, 2024 that will close this issue
Open
blairlearn added a commit that referenced this issue Mar 13, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
795a72f 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Remove comments from configuration files.
  - Config package no longer tolerates them.
- Correct repository urls and package name.

Closes #19
blairlearn added a commit that referenced this issue Mar 13, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
9f9582a 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Remove comments from configuration files.
  - Config package no longer tolerates them.
- Correct repository urls and package name.

Closes #19
blairlearn added a commit that referenced this issue Mar 13, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
dd930de 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Remove comments from configuration files.
  - Config package no longer tolerates them.
- Correct repository urls and package name.

Closes #19
blairlearn added a commit that referenced this issue Mar 14, 2024
@blairlearn
(#19) Update node to v20 (lts/iron)
ff27e2a 
- Run npm audit fix
- Bump version to 3.0.0
  - Node version is a breaking change.
  - Previous version was v2.0.1, but package.json wasn't updated.
- Remove comments from configuration files.
  - Config package no longer tolerates them.
- Correct repository urls and package name.

Closes #19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

(#20, #19) Load from filesystem. NCIOCPL/r4r-loader
1 participant
@blairlearn