-
-
Notifications
You must be signed in to change notification settings - Fork 0
3.0.6 #87
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
3.0.6 #87
Conversation
|
Caution Review failedThe pull request is closed. Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. WalkthroughThis PR performs a coordinated version bump to 3.0.6 across the monorepo, updates numerous devDependencies (Lerna 8.x→9.x, Nx 19.x→22.x, TypeScript, ESLint ecosystem packages), updates TypeScript configurations to use NodeNext module resolution strategy, adds explicit .js file extensions to ES module imports throughout the webpack-config package, and expands the public export API in the main webpack-tsparticles entry point. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Suggested labels
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (39)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR bumps the version from 3.0.3 to 3.0.6 for the tsparticles-utils monorepo packages. The main changes modernize TypeScript module configuration and align import statements with ES module standards.
- Updates TypeScript module resolution from "node"/"Node16" to "NodeNext" across multiple packages
- Adds explicit
.jsfile extensions to all relative imports to comply with ES module requirements - Updates multiple dependencies to their latest versions across the monorepo
Reviewed changes
Copilot reviewed 38 out of 40 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/webpack-config/tsconfig.json | Updates module system from "es2015" to "NodeNext" and adds ES2024/ES2023 to lib array |
| packages/webpack-config/src/**/*.ts | Adds .js extensions to all import statements for ES module compliance |
| packages/webpack-config/package.json | Version bump to 3.0.6 and updates multiple dependencies |
| packages/webpack-config/CHANGELOG.md | Adds changelog entries for versions 3.0.5 and 3.0.6 |
| packages/tsconfig/tsconfig*.json | Updates module resolution strategies across different build targets |
| packages/tsconfig/package.json | Version bump to 3.0.6 and TypeScript version update |
| packages/tsconfig/CHANGELOG.md | Adds changelog entries for versions 3.0.4, 3.0.5, and 3.0.6 |
| packages/prettier-config/package.json | Version bump to 3.0.6 and dependency updates |
| packages/prettier-config/CHANGELOG.md | Adds changelog entry for version 3.0.6 |
| packages/eslint-config/tsconfig.json | Changes module resolution from "Bundler" to "NodeNext" |
| packages/eslint-config/package.json | Version bump to 3.0.6 and updates multiple development dependencies |
| packages/eslint-config/CHANGELOG.md | Adds changelog entries for versions 3.0.5 and 3.0.6 |
| package.json | Updates root-level dependencies (lerna, nx, typescript) |
| lerna.json | Updates monorepo version to 3.0.6 |
| CHANGELOG.md | Adds root changelog entries for versions 3.0.4, 3.0.5, and 3.0.6 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "module": "Node16", | ||
| "moduleResolution": "Node16" | ||
| "module": "NodeNext", | ||
| "moduleResolution": "NodeNext", |
Copilot
AI
Dec 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trailing comma added after the last property in the compilerOptions object. This could cause issues with strict JSON parsers, though most modern TypeScript tooling accepts it. For consistency with JSON standards and to avoid potential parsing issues in some tools, consider removing the trailing comma.
| "moduleResolution": "NodeNext", | |
| "moduleResolution": "NodeNext" |
| "ES2015", | ||
| "ES5", | ||
| "DOM" | ||
| "DOM", |
Copilot
AI
Dec 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trailing comma added after "DOM" in the lib array. While TypeScript accepts this, for consistency with JSON standards and to avoid potential parsing issues in some tools, consider removing the trailing comma.
| "DOM", | |
| "DOM" |
| "compilerOptions": { | ||
| "module": "ESNext" | ||
| "module": "ESNext", | ||
| "moduleResolution": "Node", |
Copilot
AI
Dec 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trailing comma added after the last property in the compilerOptions object. For consistency with JSON standards and to avoid potential parsing issues in some tools, consider removing the trailing comma.
| "moduleResolution": "Node", | |
| "moduleResolution": "Node" |
| "compilerOptions": { | ||
| "module": "UMD" | ||
| "module": "UMD", | ||
| "moduleResolution": "Node" |
Copilot
AI
Dec 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The moduleResolution is set to "Node" while other tsconfig files in the package are being updated to use "NodeNext" (see packages/tsconfig/tsconfig.json and packages/tsconfig/tsconfig.base.json). For consistency and to align with modern Node.js module resolution, consider using "NodeNext" instead of "Node" unless there's a specific reason to use the older resolution strategy for UMD builds.
| "moduleResolution": "Node" | |
| "moduleResolution": "NodeNext" |
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.