Update: npm dependencies to latest compatible versions#610
Update: npm dependencies to latest compatible versions#610sagarjadhav wants to merge 2 commits intomainfrom
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on maintaining the project's health by updating its npm dependencies. By bringing various Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates npm dependencies, including major version bumps for @wordpress/env and eslint. Major version updates can introduce breaking changes. The associated risks and lack of information about compatibility testing are highlighted in the review comments. It is crucial to ensure these updates do not disrupt the development workflow or CI pipeline.
package.json
Outdated
| "@wordpress/scripts": "31.4.0", | ||
| "@wordpress/babel-preset-default": "8.40.0", | ||
| "@wordpress/browserslist-config": "6.40.0", | ||
| "@wordpress/env": "11.0.0", |
There was a problem hiding this comment.
The major version update of @wordpress/env from v10 to v11 introduces a high risk of breaking the local development environment due to potential breaking changes. To ensure a smooth transition, it's important to also include any necessary configuration updates and summarize the impact and testing in the PR description.
package.json
Outdated
| "cross-env": "10.1.0", | ||
| "css-minimizer-webpack-plugin": "7.0.4", | ||
| "eslint": "9.39.2", | ||
| "eslint": "10.0.2", |
There was a problem hiding this comment.
Updating eslint across a major version (v9 to v10) can introduce breaking changes and new rules. This can affect the CI/CD pipeline and developer workflow. To mitigate this risk, please include any necessary updates to the ESLint configuration and provide context on the changes in the PR description.
1 participant
Description
This PR updates and aligns project dependencies to maintain compatibility with the current development ecosystem and ensure overall build stability.
No functional or UI changes are introduced.
Technical Details
Updated Runtime Dependency
@wordpress/interactivity: 6.39.0 → 6.40.0Updated WordPress Tooling (devDependencies)
@wordpress/babel-preset-default: 8.39.0 → 8.40.0@wordpress/browserslist-config: 6.39.0 → 6.40.0@wordpress/env: 10.39.0 → 11.0.0@wordpress/eslint-plugin: 24.1.0 → 24.2.0@wordpress/jest-preset-default: 12.39.0 → 12.40.0@wordpress/scripts: 31.4.0 → 31.5.0Updated Tooling / Linting Stack
eslint: 9.39.2 → 10.0.2eslint-plugin-jest: 29.12.1 → 29.15.0Notes
@wordpress/*packages were upgraded together to maintain version alignment.@wordpress/envwas upgraded to a new major version (11.0.0) and validated locally.@wordpress/scriptssetup.webpack-dev-serveroverride (^5.2.1) remains unchanged.--experimental-modulesflag remains in use and was validated during build.Validation Performed
npm run build:devnpm run build:prodnpm run lint:allnpm run test:jswp-envNo regressions observed.
Checklist
@wordpress/interactivity@wordpress/*devDependencies in sync@wordpress/envto v11package-lock.jsonScreenshots
Not applicable — no UI or functional changes.
Fixes/Covers issue
Fixes #609