chore: try v3.11

[danielroe]

Summary by CodeRabbit

• New Features
  • Introduced a new 'nuxt-vite-config' module for configuring Vite settings in Nuxt projects, enhancing build performance and compatibility.
• Refactor
  • Updated module import paths to use relative instead of absolute paths, improving project structure and maintainability.
  • Adjusted function declaration syntax across several modules for consistency and readability.
• Tests
  • Updated snapshot test values for bundle sizes to reflect recent optimizations.

[coderabbitai]

Important

Auto Review Skipped

Review was skipped due to path filters

Files ignored due to path filters (2)

• budget.json is excluded by: !**/*.json
• pnpm-lock.yaml is excluded by: !**/*.yaml

Walkthrough

The overarching change involves refining the import paths and syntax across several modules of a Nuxt project, focusing on enhancing compatibility and readability. This includes transitioning from absolute to relative import paths, adjusting function declaration styles, and a minor update in file size for snapshot tests, indicating a slight optimization in bundle sizes.

Changes

Files	Change Summary
src/modules/bundle.ts	Introduced a new file for configuring Vite settings in Nuxt projects, with conditional Vite options setup.
src/modules/components-chunk.ts, src/modules/dedupe-hoisted.ts, src/modules/reduce-chunks.ts, src/modules/sitemap.ts, src/modules/tree-shake.ts	Updated import paths to relative and modified function declarations to include spaces before parentheses.
test/unit/bundle.spec.ts	Updated snapshot test values for file sizes, indicating slight changes in the bundle sizes.

🐰✨

In the land of code, where the bits do roam,
A rabbit hopped in, making Nuxt its home.
With a tweak and a twist, imports found their way,
Spaces before parentheses, here to stay.
🌟 Bundles shrink, ever so slight,
In this digital burrow, all is right.
🐾🥕

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
roe.dev	✅ Ready (Inspect)	Visit Preview	Mar 17, 2024 0:39am

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@atproto/api@0.11.2	Transitive: network	+7	13.1 MB	dholms
npm/@commitlint/cli@19.2.0	Transitive: environment, eval, filesystem, shell, unsafe	+60	7.19 MB	escapedcat
npm/@commitlint/config-conventional@19.1.0	Transitive: filesystem	+9	2.15 MB	escapedcat
npm/@iconify-json/tabler@1.1.108	None	+1	1.78 MB	cyberalien
npm/@nuxt/fonts@0.3.0	network Transitive: environment, eval, filesystem, shell, unsafe	+76	20.8 MB	danielroe
npm/@unhead/vue@1.8.20	environment	+3	225 kB	harlan_zw
npm/@unocss/nuxt@0.58.6	Transitive: environment, filesystem, network, shell, unsafe	+92	11.8 MB	antfu
npm/@unocss/postcss@0.58.6	Transitive: filesystem, unsafe	+19	2.9 MB	antfu
npm/@unocss/reset@0.58.6	None	0	43.9 kB	antfu
npm/@vue/test-utils@2.4.5	eval Transitive: environment, filesystem, network, shell	+19	4.85 MB	lmiller1990
npm/happy-dom@13.8.6	network, shell, unsafe	+1	9.11 MB	davidortner
npm/masto@6.7.0	network	+10	602 kB	neetshin

🚮 Removed packages: npm/@atproto/api@0.10.5, npm/@commitlint/cli@19.0.3, npm/@commitlint/config-conventional@19.0.3, npm/@iconify-json/tabler@1.1.106, npm/@nuxt/fonts@0.0.2, npm/@nuxt/kit@3.10.3, npm/@unhead/vue@1.8.11, npm/@unocss/nuxt@0.58.5, npm/@unocss/postcss@0.58.5, npm/@unocss/reset@0.58.5, npm/@vue/test-utils@2.4.4, npm/happy-dom@13.6.2, npm/masto@6.6.4, npm/nitropack@2.9.1, npm/nuxt@3.10.3

View full report↗︎

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b5cdeb2 and 2e78d63.

Files ignored due to path filters (3)

• budget.json is excluded by: !**/*.json
• package.json is excluded by: !**/*.json
• pnpm-lock.yaml is excluded by: !**/*.yaml

Files selected for processing (7)

• src/modules/bundle.ts (1 hunks)
• src/modules/components-chunk.ts (1 hunks)
• src/modules/dedupe-hoisted.ts (4 hunks)
• src/modules/reduce-chunks.ts (1 hunks)
• src/modules/sitemap.ts (1 hunks)
• src/modules/tree-shake.ts (1 hunks)
• test/unit/bundle.spec.ts (2 hunks)

Additional comments: 13

src/modules/reduce-chunks.ts (2)

• 1-1: The import statement has been updated to use a local path (nuxt/kit) instead of a package path, aligning with the PR objectives to standardize import paths.
• 7-7: The function declaration syntax has been changed from setup() to setup (), adding a space before the parentheses. This is a stylistic change likely aimed at consistency across the project.

src/modules/bundle.ts (2)

• 1-3: The import statements use local paths (nuxt/kit and defu), which is consistent with the PR objectives to standardize import paths.
• 4-24: The module is correctly defined with a meta object specifying its name, and the Vite configuration is conditionally set up based on an environment variable. This aligns with Nuxt module standards and is a targeted improvement to the project's build process.

src/modules/sitemap.ts (2)

• 3-3: The import statement has been updated to use a local path (nuxt/kit), aligning with the PR objectives to standardize import paths.
• 10-10: The function declaration syntax has been changed from setup() to setup (), adding a space before the parentheses. This is a stylistic change aimed at consistency across the project.

src/modules/tree-shake.ts (2)

• 1-1: The import statement uses a local path (nuxt/kit), which is consistent with the PR objectives to standardize import paths.
• 9-9: The function declaration syntax has been changed to add a space before the parentheses in both setup and transform functions. This is a stylistic change aimed at consistency across the project.

Also applies to: 13-13

src/modules/components-chunk.ts (2)

• 1-1: The import statement uses a local path (nuxt/kit), which is consistent with the PR objectives to standardize import paths.
• 7-7: The function declaration syntax has been changed from setup() to setup (), adding a space before the parentheses. This is a stylistic change aimed at consistency across the project.

src/modules/dedupe-hoisted.ts (2)

• 1-1: The import paths have been updated from @nuxt/kit to nuxt/kit, aligning with the PR objectives to standardize import paths.
• 11-11: Method signatures within the createUnplugin object and the setup function within the exported Nuxt module have been adjusted by adding spaces before the parentheses. This is a stylistic change aimed at consistency across the project.

Also applies to: 14-14, 44-44, 54-54

test/unit/bundle.spec.ts (1)

• 39-39: The snapshot test values for file sizes have been updated to reflect slight adjustments in the project's output. This suggests that the modifications in the project's configuration and structure have tangible impacts on the build output.

Also applies to: 82-82, 87-87