Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. WalkthroughReworks size-limit action: adds debug logging, improves file→package detection by traversing up to the nearest package.json with a regex fallback, auto-excludes peerDependencies from bundle checks, updates package size-limit ignore lists, and enables manual workflow_dispatch triggering. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Poem
Pre-merge checks and finishing touches❌ Failed checks (2 inconclusive)
✅ Passed checks (3 passed)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
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 |
commit: |
📦 Bundle Size Report
✅ All size limits passed! |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
.github/actions/size-limit/src/index.ts (1)
74-74: Enhance debugging to diagnose filtering issues.The added console.log is helpful but may not reveal why results are being filtered out (which appears to be the root cause when line 76 triggers). When
filteredResults.length === 0butresults.length > 0, logging the already-filtered result will only show "No results found."Consider adding additional debug logs before filtering to better diagnose the issue:
// Run size-limit on current branch const { results, hasErrors } = await runSizeLimit(config.filter); +// Debug: Log results before filtering +console.log(`🔍 Found ${results.length} total results before filtering`); +console.log(`🔍 Changed packages: ${changedPackages ? Array.from(changedPackages).join(', ') || '(none)' : '(all)'}`); + // Filter results to only include changed packages (if in PR context) const filteredResults = filterChangedPackages(results, changedPackages); +console.log(`🔍 ${filteredResults.length} results after filtering`); + // Log baseline and current sizes for debugging (especially for release PRs) logDebugInfo(filteredResults, baselineSizes, config.isReleasePR);This would reveal whether the issue is in change detection (
changedPackages), in the filtering logic (filterChangedPackages), or in result parsing (resultsbeing empty)..github/actions/size-limit/src/size-limit/package.ts (1)
95-113: Peer dependencies auto‑ignore is sound; consider small clarity/perf tweaks.The new logic that appends
Object.keys(packageJson.peerDependencies)intoignoreis consistent with treating peers as externals and should reduce noisy size-limit failures from heavy peer deps.Two optional polish ideas:
- Precompute
const peerDeps = packageJson.peerDependencies ? Object.keys(packageJson.peerDependencies) : [];once outside themapand reuse it, instead of recomputing inside each callback.- If you expect
ignoreto grow further, you might wrap the final array in anew Set([...])to dedupe values before passing to size-limit/esbuild.Both are non-blocking; current implementation is correct as-is.
.github/actions/size-limit/src/package/changes.ts (1)
65-110: Package resolution traversal looks solid; be aware ofpackages/<file>edge caseThe new “nearest
package.json” traversal plus scoped fallback regex is a nice improvement in robustness and should behave well for the usual layouts:
packages/pkg/...→ resolvespackages/pkg/package.json.packages/@scope/pkg/...→ resolvespackages/@scope/pkg/package.json.- Deleted or unreadable
package.json→ regex fallback still inferspkg/@scope/pkg.One edge case to be aware of:
- For files directly under
packages/(e.g.packages/package.json,packages/README.md), the loop never finds a non‑emptypotentialPackageDir, and the fallback regex^packages\/((?:@[^/]+\/)?[^/]+)\/requires a trailing/, so those paths won’t map to any package at all. If such files exist and should trigger “treat as all packages changed” (or be mapped specially), you may want to either:
- Handle
packages/package.jsonexplicitly before the loop, or- Relax the fallback pattern to also match without a trailing slash and then treat that as a special “workspace” signal in the caller.
If you’re confident nothing relevant lives directly under
packages/, the current behavior is fine and the change overall looks good.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (7)
.github/actions/size-limit/src/index.ts(1 hunks).github/actions/size-limit/src/package/changes.ts(1 hunks).github/actions/size-limit/src/size-limit/package.ts(2 hunks).github/workflows/size-limit.yml(2 hunks)packages/arkenv/package.json(1 hunks)packages/bun-plugin/package.json(1 hunks)packages/vite-plugin/package.json(1 hunks)
🧰 Additional context used
📓 Path-based instructions (4)
packages/*/package.json
📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)
Packages in packages/ directory must be published to npm and require changesets for versioning, proper exports, and type definitions
Files:
packages/arkenv/package.jsonpackages/bun-plugin/package.jsonpackages/vite-plugin/package.json
**/package.json
📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)
Use workspace:* protocol for workspace dependencies between packages
Files:
packages/arkenv/package.jsonpackages/bun-plugin/package.jsonpackages/vite-plugin/package.json
{packages,apps,tooling}/**/package.json
📄 CodeRabbit inference engine (.cursor/rules/pnpm.mdc)
When referencing workspace packages in dependencies, use the
workspace:*protocol instead of version numbers
Files:
packages/arkenv/package.jsonpackages/bun-plugin/package.jsonpackages/vite-plugin/package.json
**/*.{ts,tsx,json,md}
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Use Biome for linting and formatting instead of ESLint and Prettier
Files:
packages/arkenv/package.jsonpackages/bun-plugin/package.jsonpackages/vite-plugin/package.json
🧠 Learnings (34)
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Leverage ArkType's type inference for TypeScript types instead of manual type definitions
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Keep environment variable schemas readable and TypeScript-like using ArkType syntax
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Use union types for enums in ArkType schemas (e.g., `"'dev' | 'prod'"`) instead of separate enum definitions
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-29T22:11:39.931Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-29T22:11:39.931Z
Learning: Applies to packages/arkenv/src/**/*.ts : Main library implementation should be in `src/create-env.ts`, built-in validators in `src/types.ts`, error handling in `src/errors.ts`, and utilities in `src/utils.ts`
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Leverage ArkType's built-in types (e.g., `string.host`, `number.port`) where possible in environment schemas
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-29T08:00:08.044Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-29T08:00:08.044Z
Learning: Applies to package.json : Configure only built dependencies (native modules) in `pnpm.onlyBuiltDependencies`, including: biomejs/biome, sentry/cli, swc/core, tailwindcss/oxide, vercel/speed-insights, esbuild, and sharp
Applied to files:
packages/arkenv/package.json.github/actions/size-limit/src/size-limit/package.tspackages/bun-plugin/package.jsonpackages/vite-plugin/package.json
📚 Learning: 2025-11-24T16:04:11.901Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.901Z
Learning: Applies to tooling/*/package.json : Tooling in tooling/ directory contains development and testing tools that are not published to npm and excluded from changesets
Applied to files:
packages/arkenv/package.json.github/actions/size-limit/src/size-limit/package.tspackages/bun-plugin/package.jsonpackages/vite-plugin/package.json.github/actions/size-limit/src/package/changes.ts
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Use ArkType's `type()` function to define schemas in environment variable definitions
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-24T16:04:11.901Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.901Z
Learning: Applies to packages/*/package.json : Packages in packages/ directory must be published to npm and require changesets for versioning, proper exports, and type definitions
Applied to files:
packages/arkenv/package.json.github/actions/size-limit/src/size-limit/package.tspackages/bun-plugin/package.json.github/actions/size-limit/src/package/changes.ts
📚 Learning: 2025-11-24T16:03:45.295Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/arktype.mdc:0-0
Timestamp: 2025-11-24T16:03:45.295Z
Learning: Applies to packages/arkenv/**/*.ts : Use the scoped `$` type system for custom types defined in `scope.ts`
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-11-24T16:04:00.957Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/coding-guidelines.mdc:0-0
Timestamp: 2025-11-24T16:04:00.957Z
Learning: Applies to **/*.{ts,tsx} : Organize imports automatically (Biome handles this)
Applied to files:
packages/arkenv/package.jsonpackages/vite-plugin/package.json
📚 Learning: 2025-11-24T16:04:00.957Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/coding-guidelines.mdc:0-0
Timestamp: 2025-11-24T16:04:00.957Z
Learning: Prefer tree-shakeable exports for better bundling
Applied to files:
packages/arkenv/package.json.github/actions/size-limit/src/size-limit/package.tspackages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/package.json : Use `bun install` instead of `npm install`, `yarn install`, or `pnpm install` for dependency management
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/package.json : Use `bun install` instead of `npm install`, `yarn install`, or `pnpm install`
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/package.json : Use `bun run <script>` instead of `npm run <script>`, `yarn run <script>`, or `pnpm run <script>`
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:47.583Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:47.583Z
Learning: Applies to apps/playgrounds/bun-react/**/package.json : Use `bun install` instead of `npm install`, `yarn install`, or `pnpm install` in package.json scripts
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:47.583Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:47.583Z
Learning: Applies to apps/playgrounds/bun-react/**/package.json : Use `bun run <script>` instead of `npm run <script>`, `yarn run <script>`, or `pnpm run <script>` in package.json scripts
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/package.json : Use `bun run <script>` instead of `npm run <script>`, `yarn run <script>`, or `pnpm run <script>` for running scripts
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T22:11:39.931Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-29T22:11:39.931Z
Learning: Consider bundle size impact when adding new dependencies - aspirational goal: <1kB gzipped, enforced limit: 2kB gzipped
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:47.583Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:47.583Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx,html} : CSS files can be imported directly in TypeScript/JavaScript or referenced in HTML `<link>` tags, and Bun will automatically bundle them
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/*.{ts,tsx,js,jsx} : Prefer `Bun.file` over `node:fs`'s readFile/writeFile
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/*.html : HTML files can import .tsx, .jsx, or .js files directly; Bun will automatically transpile and bundle
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,tsx,js,jsx} : Bun automatically loads .env files, so don't use `dotenv` library
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,tsx,js,jsx} : Prefer `Bun.file` over `node:fs` readFile/writeFile for file operations
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:47.583Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:47.583Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx} : Prefer `Bun.file` over `node:fs` readFile/writeFile methods for file operations
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/*.html : HTML files can import .tsx, .jsx, or .js files directly which Bun will transpile and bundle automatically
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/*.{ts,tsx,js,jsx} : Use `bun <file>` instead of `node <file>` or `ts-node <file>`
Applied to files:
packages/bun-plugin/package.json
📚 Learning: 2025-11-24T16:04:11.901Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.901Z
Learning: packages/arkenv should not depend on other workspace packages; packages/vite-plugin depends on arkenv; apps/www may depend on workspace packages
Applied to files:
packages/vite-plugin/package.json
📚 Learning: 2025-11-24T16:04:47.583Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:47.583Z
Learning: Applies to apps/playgrounds/bun-react/**/*.html : Use HTML imports with `Bun.serve()` and don't use Vite for frontend bundling and development
Applied to files:
packages/vite-plugin/package.json
📚 Learning: 2025-11-24T16:04:58.629Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: apps/playgrounds/bun/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:58.629Z
Learning: Applies to apps/playgrounds/bun/**/*.{html,tsx,jsx} : Use HTML imports with `Bun.serve()` instead of Vite for frontend development
Applied to files:
packages/vite-plugin/package.json
📚 Learning: 2025-11-29T08:57:24.056Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: examples/with-bun-react/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc:0-0
Timestamp: 2025-11-29T08:57:24.056Z
Learning: Applies to examples/with-bun-react/**/*.html : Use HTML imports with `Bun.serve()` instead of `vite` for frontend builds
Applied to files:
packages/vite-plugin/package.json
📚 Learning: 2025-11-29T22:11:39.931Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-29T22:11:39.931Z
Learning: Always run `pnpm changeset` for version bumps in published packages - never skip changesets
Applied to files:
.github/actions/size-limit/src/package/changes.ts
📚 Learning: 2025-11-24T16:04:11.901Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.901Z
Learning: Only packages in packages/ directory are published to npm; publishing is handled by changesets using pnpm release
Applied to files:
.github/actions/size-limit/src/package/changes.ts
📚 Learning: 2025-11-29T08:00:08.044Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-29T08:00:08.044Z
Learning: Organize workspace packages into appropriate directories: `packages/` for published npm packages, `apps/` for applications, `tooling/` for development tools (not published), and `examples/` for example projects
Applied to files:
.github/actions/size-limit/src/package/changes.ts
🧬 Code graph analysis (1)
.github/actions/size-limit/src/index.ts (1)
.github/actions/size-limit/src/output.ts (1)
results(4-21)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: test-e2e (e2e)
- GitHub Check: test-e2e (a11y)
- GitHub Check: test-build (lts/*)
- GitHub Check: test-build (latest)
🔇 Additional comments (5)
.github/workflows/size-limit.yml (2)
8-8: Manual trigger addition looks good.Adding
workflow_dispatch:supports manual workflow runs for debugging purposes, which aligns well with the PR objective to investigate parsing failures.
28-28: Verify paths-filter behavior with workflow_dispatch events.The
dorny/paths-filteraction is designed primarily forpull_requestevents. When the workflow is manually triggered viaworkflow_dispatch, the filter may not behave as expected (no PR context), potentially causingchanges.outputs.packagesto be undefined or false—which would prevent the size-limit job from running even when manually dispatched.Consider one of these approaches:
- Explicitly handle the
workflow_dispatchcase by checking both conditions separately in the job condition, or- Verify the actual output behavior of paths-filter on workflow_dispatch events and adjust the condition if needed.
packages/arkenv/package.json (1)
56-65: Verify size-limit configuration syntax and effectiveness in resolving parsing failures.The changes add
"import": "*"alongside an"ignore"array to exclude peerDependencies from size calculations. This pattern appears intended to fix the intermittent "Could not parse size-limit output" failures from issue #502.Please confirm:
- This
"import": "*"+"ignore": [...]configuration is valid for your version of size-limit- These changes actually resolve the intermittent parsing failures observed in #502
You may also want to run
pnpm -w run sizeon this package to verify the configuration works locally before merging.packages/vite-plugin/package.json (1)
62-72: Verify size-limit configuration matches expected behavior.The ignore list correctly excludes both peerDependencies (vite and arktype) from size calculations. Verify that this configuration works as expected with your version of size-limit.
Also ensure that the bundled size of this package remains under the 2 kB limit with these exclusions in place.
packages/bun-plugin/package.json (1)
62-75: Verify that Node built-in module exclusions in ignore list are appropriate.The ignore list properly excludes peerDependencies (bun, arktype) and additionally excludes Node built-in modules. Confirm that:
- Size-limit configuration syntax is valid for your version
- These Node built-in exclusions (node:path, node:fs, node:process) are intentional and necessary for accurate size measurement
This is the most extensive ignore list across the three packages—verify it aligns with the plugin's actual imports.
Close #502
Summary by CodeRabbit
New Features
Bug Fixes
Chores
✏️ Tip: You can customize this high-level summary in your review settings.