Update Node, npm versions and dependencies #1052
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated Node.js and npm to versions 18 and 9 respectively. Updated versions of many npm packages in both devDependencies and dependencies in package.json. Various version updates were also reflected in package-lock.json.
The version of Node.js used in the GitHub workflow has been updated to version 18. This ensures consistency with the recently updated versions in other areas of the project.
The version of Node.js used in the GitHub workflow has been increased to version 18. This change aligns the version used in the workflow with those used in other parts of the application.
The npm version required for the application has been updated from 9 to 10. This version change ensures consistency and compatibility with other parts of the application infrastructure.
The node version used in the GitHub workflows and specified in package.json has been upgraded from 18 to 20. The npm version range has also been slightly adjusted in package.json. The modifications intend to keep the system updated and address potential compatibility issues.
The versions of various "@WordPress" dependencies in both "package.json" and "package-lock.json" files are downgraded to match WP 6.4.2. This includes a switch to previous versions for packages such as "@wordpress/dependency-extraction-webpack-plugin", "@wordpress/a11y", "@wordpress/annotations", among others. Adjustments aim to improve compatibility and address potential issues with the specific project's environment or other dependencies.
The 'frontend.jsx' file under 'admin-settings' in the assets/js directory now uses the new React root API for rendering. The root API creates a root from a container and allows rendering operations to be scheduled over time. Instead of rendering directly in the component, a constant container is declared and then a root is created from this container for the rendering process.
This change transforms functional components across several files to use the 'function' keyword instead of arrow functions. It adheres to the project coding style guide and aids in debugging by providing more descriptive function names in stack traces. The code refactoring was applied consistently for all functional components in affected files. No functionality changes were made.
This commit increases the maximum acceptable Node.js version in package.json and updates the Node.js versions in the node-tests.yml and built-release.yml workflow files to version 21. This change helps maintain software alignment with updated technologies and enhances compatibility.
Numerous package dependencies have been updated in package-lock.json. Significant changes largely involve updates to allow for newer versions of packages, some removals due to redundancy or changes in codebase, and a few version-specific updates. This will help maintain alignment with contemporary packages.
The function fetchTerm in use-term-cache service now accepts term ID as a string. It then converts this string to a number and verifies its validity before proceeding. This update improves error handling by ensuring the term ID received is a valid number.
Update term ID type handling in fetchTerm function
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Node.js and npm to versions 18 and 9 respectively. Updated versions of many npm packages in both devDependencies and dependencies in package.json. Various version updates were also reflected in package-lock.json.
Fixes #1051