Skip to content

Conversation

@xvaara
Copy link
Contributor

@xvaara xvaara commented Apr 30, 2025

BEGIN_COMMIT_OVERRIDE
chore: update depencies
END_COMMIT_OVERRIDE# Describe the PR

A clear and concise description of what the pull request does.

Small replication

A small replication or video walkthrough can help demonstrate the changes made. This is optional, but can help observe the intended changes. A mentioned issue that contains a replication also works.

PR checklist

What kind of change does this PR introduce? (check at least one)

  • Bugfix 🐛 - fix(...)
  • Feature - feat(...)
  • ARIA accessibility - fix(...)
  • Documentation update - docs(...)
  • Other (please describe)

The PR fulfills these requirements:

  • Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

Summary by CodeRabbit

  • New Features
    • Migrated the Nuxt module to ES module format for improved compatibility.
  • Chores
    • Updated multiple dependencies across the project to their latest versions for enhanced stability and compatibility.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 30, 2025

Walkthrough

This set of changes updates the dependency versions across multiple package.json files in various projects and packages. The updates primarily involve bumping patch and minor versions of development and core dependencies such as TypeScript, ESLint, Bootstrap, Vite, and related tooling. In addition, the Nuxt module package transitions from CommonJS to ES module format, updating its main entry point, exports, and type declarations accordingly. No source code, configuration, or script logic was altered, and there were no modifications to exported or public entities except for the Nuxt package metadata.

Changes

File(s) Change Summary
apps/docs/package.json Updated devDependencies: bumped versions for @tsconfig/node22, @types/node, bootstrap, eslint, eslint-plugin-vue, typescript, and unplugin-vue-components.
apps/playground/package.json Updated dependencies: bumped vue-router. Updated devDependencies: bumped @tsconfig/node22, @types/node, bootstrap, typescript, vite, and vue-tsc.
package.json Bumped versions for devDependencies: lint-staged and turbo.
packages/bootstrap-vue-next/package.json Updated devDependencies: bumped versions for TypeScript, linting, testing, build, and Vue-related packages.
packages/nuxt/package.json Migrated to ES module format: changed main entry to .mjs, updated exports, removed CommonJS entry, changed types path, removed top-level types field. Bumped dependency versions for Nuxt ecosystem and tooling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant NuxtPkg as Nuxt Package
    participant NodeJS

    User->>NuxtPkg: Import package
    NuxtPkg->>NodeJS: Resolve "main" as ./dist/module.mjs (ESM)
    NuxtPkg->>NodeJS: Provide types from ./dist/types.d.mts
    Note right of NuxtPkg: CommonJS entry removed
Loading

Poem

Springtime hops through package trees,
With version bumps on every breeze.
ES modules now in sight,
Dependencies polished bright.
No scripts disturbed, no code askew—
Just fresher carrots for the crew!
🥕✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f046c68 and aa999ab.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • apps/docs/package.json (1 hunks)
  • apps/playground/package.json (1 hunks)
  • package.json (1 hunks)
  • packages/bootstrap-vue-next/package.json (2 hunks)
  • packages/nuxt/package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (5)
package.json (1)

51-52: Approve root devDependencies bumps
The updates for lint-staged to ^15.5.1 and turbo to ^2.5.2 keep the monorepo tooling versions consistent and mitigate the open latest tag risk.

apps/docs/package.json (1)

21-22: Approve docs devDependencies version updates
All bumped patches/minors—@tsconfig/node22, @types/node, bootstrap, eslint, eslint-plugin-vue, typescript, and unplugin-vue-components—align with the monorepo’s other packages and introduce no breaking changes.

Also applies to: 27-27, 30-32, 34-34, 36-36

apps/playground/package.json (1)

17-17: Approve playground dependency and devDependency bumps
Updating vue-router, @tsconfig/node22, @types/node, bootstrap, typescript, vite, and vue-tsc ensures consistency across apps and leverages the latest patches.

Also applies to: 20-22, 24-27

packages/bootstrap-vue-next/package.json (1)

166-196: Approve bootstrap-vue-next devDependencies upgrades
A broad set of devDependencies—including TypeScript utilities, ESLint, Vitest, Sass, Vite plugins, and Bootstrap itself—have been bumped to patch/minor revisions in lockstep with the monorepo. No API-affecting changes are expected.

packages/nuxt/package.json (1)

11-16: Approve Nuxt module ESM migration & dependency upgrades
The main entrypoint is correctly switched to .mjs with matching .d.mts type exports, and all key dependencies (@nuxt/kit, devtools, builder, schema, ESLint, Nuxt core, TypeScript, Unimport) are aligned with the rest of the repo.

Please confirm that the CI pipelines and consuming Nuxt projects load the ESM entrypoints without regressions.

Also applies to: 37-44, 46-46, 49-55


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Apr 30, 2025

bsvn-vite-ts

npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next@2676
npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next/@bootstrap-vue-next/nuxt@2676

commit: aa999ab

@xvaara xvaara merged commit 05f8737 into main Apr 30, 2025
5 checks passed
@xvaara xvaara deleted the up-deps-2025-04 branch April 30, 2025 12:11
@coderabbitai coderabbitai bot mentioned this pull request Aug 4, 2025
6 tasks
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.

2 participants