Skip to content

chore(deps): Update Node.js version and package dependencies #31990

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

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

oidacra
Copy link
Member

@oidacra oidacra commented Apr 25, 2025

  • Updated Node.js version in and to v22.15.0.
  • Adjusted package dependencies in , including updates to , , and various Babel packages for improved compatibility and performance.
  • Enhanced type imports in for better type safety and clarity in Angular component properties.
  • Refactored to streamline imports and improve code organization.

These changes aim to ensure compatibility with the latest Node.js features and enhance overall project maintainability.

- Updated Node.js version in  and  to v20.19.1.
- Adjusted package dependencies in , including updates to , , and various Babel packages for improved compatibility and performance.
- Enhanced type imports in  for better type safety and clarity in Angular component properties.
- Refactored  to streamline imports and improve code organization.

These changes aim to ensure compatibility with the latest Node.js features and enhance overall project maintainability.
@oidacra oidacra marked this pull request as ready for review April 25, 2025 14:52
oidacra added 2 commits April 25, 2025 11:06
- Updated the Node.js version in  and  to v20.19.1 for improved compatibility and performance.
- Updated Node.js version in .nvmrc and core-web/.nvmrc to v22.15.0 for improved compatibility and performance.
- Adjusted package.json to reflect the new Node.js version requirement.
xmlbuilder "15.1.1"

node-forge@1.3.1:

Choose a reason for hiding this comment

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

Legal Risk

node-forge 1.3.1 was released under the GPL-2.0 license, a license that
has been flagged by your organization for consideration.

Recommendation

While merging is not directly blocked, it's best to pause and consider what it means to use this license before continuing. If you are unsure, reach out to your security team or Semgrep admin to address this issue.

zJaaal
zJaaal previously requested changes Apr 28, 2025
Comment on lines +44 to +55
setHighlight:
() =>
({ commands }) => {
// Implementa la lógica de highlight aquí
return true;
},
unsetHighlight:
() =>
({ commands }) => {
// Implementa la lógica para remover el highlight aquí
return true;
},
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need this?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, without that, the component will not build.

setHighlight:
() =>
({ commands }) => {
// Implementa la lógica de highlight aquí
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove comment? Or translate them to en?

Comment on lines +79 to +80
<!-- Force to use node v18.20.3 -->
<node.js.version>v18.20.3</node.js.version>
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we forcing node v18 here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Testing purposes.

"main": "index.js",
"license": "MIT",
"dependencies": {
"newman": "^6.2.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need a BE checking that this doesn't break anything?

Copy link
Contributor

Choose a reason for hiding this comment

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

Only formatting, right?

Copy link
Contributor

Choose a reason for hiding this comment

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

Same

@@ -131,7 +131,7 @@ test-integration-stop:
./mvnw -pl :dotcms-integration -Pdocker-stop -Dcoreit.test.skip=false

test-postman-ide:
./mvnw -pl :dotcms-test-karate pre-integration-test -Dpostman.test.skip=false -Dtomcat.port=8080
./mvnw -pl :dotcms-test-postman pre-integration-test -Dpostman.test.skip=false -Dtomcat.port=8080
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this ok?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes. Steve B asked me to fix that typo.

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

Successfully merging this pull request may close these issues.

Upgrade NodeJS from v22.15.0 to newer version due to EOL
3 participants