Skip to content

Migrate from npx#434

Merged
yamcodes merged 1 commit intomainfrom
432-switch-from-npx-to-pnpm-exec-or-pnpm-dlx-pnpx-wherever-possible
Nov 24, 2025
Merged

Migrate from npx#434
yamcodes merged 1 commit intomainfrom
432-switch-from-npx-to-pnpm-exec-or-pnpm-dlx-pnpx-wherever-possible

Conversation

@yamcodes
Copy link
Owner

@yamcodes yamcodes commented Nov 24, 2025

Closes #432

  • Changed package installation commands from npm to bun in the size-limit action for better compatibility.
  • Updated development script in package.json to utilize pnpm for executing next-video sync.
  • Modified build script to spawn commands using pnpm instead of npx, ensuring consistency in package management across the project.

Summary by CodeRabbit

  • Chores
    • Updated build and development workflow tooling to use alternative package managers for improved build execution and dependency management consistency.

✏️ Tip: You can customize this high-level summary in your review settings.

- Changed package installation commands from npm to bun in the size-limit action for better compatibility.
- Updated development script in package.json to utilize pnpm for executing next-video sync.
- Modified build script to spawn commands using pnpm instead of npx, ensuring consistency in package management across the project.
@yamcodes yamcodes linked an issue Nov 24, 2025 that may be closed by this pull request
@changeset-bot
Copy link

changeset-bot bot commented Nov 24, 2025

⚠️ No Changeset found

Latest commit: d84e2a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Nov 24, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
arkenv Ready Ready Preview Comment Nov 24, 2025 9:30pm

@github-actions github-actions bot added github actions Pull requests that update GitHub Actions code www Improvements or additions to arkenv.js.org labels Nov 24, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 24, 2025

Walkthrough

Migrated package execution commands from npx to alternative package runners: bun/bunx for the size-limit workflow and pnpm exec for the www application build and dev scripts. No functional logic changes were made.

Changes

Cohort / File(s) Change Summary
Size-limit workflow package runner migration
.github/actions/size-limit/src/size-limit/package.ts
Replaced npm install with bun install and npx --yes size-limit with bunx size-limit. Updated inline comment to reference bun instead of npm/npmx for peerDependencies handling.
Package execution command changes
apps/www/bin/build.js, apps/www/package.json
Replaced npx invocations with pnpm exec: changed spawned command in build.js from npx to pnpm exec, and updated dev script from npx next-video sync -w to pnpm exec next-video sync -w in package.json.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Straightforward command substitutions across multiple files
  • No logic changes or error handling modifications
  • Homogeneous pattern of replacements (npx → bun/bunx and npx → pnpm exec)
  • Consider verifying that bun and pnpm exec are properly configured in the respective environments

Possibly related PRs

Suggested labels

github_actions

Poem

🐰 A rabbit hops through package lanes,
Swapping npx for faster reins!
Bun and pnpm now take the stage,
Speeding scripts on every page.
Hoppy builds in record time! 🏃‍♂️✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Migrate from npx' clearly summarizes the main change: replacing npx with alternative package managers (pnpm and bun) across multiple files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 432-switch-from-npx-to-pnpm-exec-or-pnpm-dlx-pnpx-wherever-possible

📜 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 1143c3e and d84e2a1.

📒 Files selected for processing (3)
  • .github/actions/size-limit/src/size-limit/package.ts (3 hunks)
  • apps/www/bin/build.js (1 hunks)
  • apps/www/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (6)
apps/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Applications in apps/ directory are not published to npm and may depend on workspace packages

Files:

  • apps/www/package.json
**/package.json

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Use workspace:* protocol for workspace dependencies between packages

When referencing workspace packages, use the workspace:* protocol in dependencies

Files:

  • apps/www/package.json
{**/package.json,pnpm-lock.yaml,pnpm-workspace.yaml}

📄 CodeRabbit inference engine (.cursor/rules/pnpm.mdc)

{**/package.json,pnpm-lock.yaml,pnpm-workspace.yaml}: Always use pnpm for all package management operations
Never use npm or yarn commands

Files:

  • apps/www/package.json
{pnpm-workspace.yaml,**/package.json}

📄 CodeRabbit inference engine (.cursor/rules/pnpm.mdc)

Certain native dependencies are configured with onlyBuiltDependencies in pnpm configuration: @biomejs/biome, @sentry/cli, @swc/core, @tailwindcss/oxide, @vercel/speed-insights, esbuild, sharp

Files:

  • apps/www/package.json
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx,js,jsx}: Use createEnv(schema) function (available as default export, typically imported as arkenv) to create validated environment objects with ArkType schema definitions
Use built-in validators (host, port, url, email) from ArkEnv when available in environment schemas instead of writing custom validators
Provide default values for optional environment variables in schemas using the = value syntax
Use descriptive environment variable names that indicate purpose and format in schema definitions

Files:

  • apps/www/bin/build.js
apps/www/**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (apps/www/.cursor/rules/posthog-integration.mdc)

apps/www/**/*.{ts,tsx,js,jsx}: If using TypeScript, use an enum to store feature flag names. If using JavaScript, store feature flag names as strings to an object declared as a constant to simulate an enum. Use UPPERCASE_WITH_UNDERSCORE naming convention for enum/const object members.
If a custom property for a person or event is referenced in two or more files or two or more callsites in the same file, use an enum or const object with UPPERCASE_WITH_UNDERSCORE naming convention, similar to feature flags.

Files:

  • apps/www/bin/build.js
🧠 Learnings (23)
📓 Common learnings
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.550Z
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
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.550Z
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
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.603Z
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
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.603Z
Learning: Applies to apps/playgrounds/bun/**/package.json : Use `bun install` instead of `npm install`, `yarn install`, or `pnpm install` for dependency management
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to {**/package.json,pnpm-lock.yaml,pnpm-workspace.yaml} : Always use `pnpm` for all package management operations
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to package.json : The project uses `pnpm10.20.0` (specified in `packageManager` field)
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-24T16:03:35.734Z
Learning: Create changesets for version management using `pnpm changeset` with appropriate bump levels: patch for bug fixes, minor for new features, major for breaking changes
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-24T16:03:35.734Z
Learning: Use pnpm workspaces for package management across the monorepo instead of npm or yarn
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,tsx,js,jsx} : Use `Bun.$\`command\`` for shell execution instead of `execa`
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,js} : Use `bun <file>` instead of `node <file>` or `ts-node <file>` for running scripts
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx} : Use `Bun.$` template literal syntax for shell commands instead of `execa`
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx} : Use `bun <file>` instead of `node <file>` or `ts-node <file>` for running TypeScript and JavaScript files
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{html,ts,tsx,css} : Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild` for bundling
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx,html,css} : Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild` for bundling
📚 Learning: 2025-11-24T16:04:47.550Z
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.550Z
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:

  • apps/www/package.json
  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:58.603Z
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.603Z
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:

  • apps/www/package.json
  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:47.550Z
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.550Z
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:

  • apps/www/package.json
  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:19.392Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to {**/package.json,pnpm-lock.yaml,pnpm-workspace.yaml} : Always use `pnpm` for all package management operations

Applied to files:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:11.869Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.869Z
Learning: Only packages in packages/ directory are published to npm; publishing is handled by changesets using pnpm release

Applied to files:

  • apps/www/bin/build.js
📚 Learning: 2025-11-24T16:04:19.392Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to {pnpm-workspace.yaml,**/package.json} : Certain native dependencies are configured with `onlyBuiltDependencies` in pnpm configuration: biomejs/biome, sentry/cli, swc/core, tailwindcss/oxide, vercel/speed-insights, esbuild, sharp

Applied to files:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:03:35.734Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-24T16:03:35.734Z
Learning: Create changesets for version management using `pnpm changeset` with appropriate bump levels: patch for bug fixes, minor for new features, major for breaking changes

Applied to files:

  • apps/www/bin/build.js
📚 Learning: 2025-11-24T16:04:19.392Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Run `pnpm install` to update the lock file when dependencies change

Applied to files:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:03:35.734Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-24T16:03:35.734Z
Learning: Use Turbo for monorepo build orchestration and incremental builds, running `pnpm build` or `turbo run build`

Applied to files:

  • apps/www/bin/build.js
📚 Learning: 2025-11-24T16:03:35.734Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-24T16:03:35.734Z
Learning: Use pnpm workspaces for package management across the monorepo instead of npm or yarn

Applied to files:

  • apps/www/bin/build.js
📚 Learning: 2025-11-24T16:04:19.392Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to {**/package.json,pnpm-lock.yaml,pnpm-workspace.yaml} : Never use `npm` or `yarn` commands

Applied to files:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:58.603Z
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,tsx,js,jsx} : Use `Bun.$\`command\`` for shell execution instead of `execa`

Applied to files:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:58.603Z
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.603Z
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:

  • apps/www/bin/build.js
  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:58.603Z
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{ts,js} : Use `bun <file>` instead of `node <file>` or `ts-node <file>` for running scripts

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:47.550Z
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx} : Use `bun <file>` instead of `node <file>` or `ts-node <file>` for running TypeScript and JavaScript files

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:47.550Z
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx} : Use `Bun.$` template literal syntax for shell commands instead of `execa`

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:58.603Z
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.603Z
Learning: Applies to apps/playgrounds/bun/**/*.{html,ts,tsx,css} : Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild` for bundling

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:47.550Z
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.550Z
Learning: Applies to apps/playgrounds/bun-react/**/*.{ts,tsx,js,jsx,html,css} : Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild` for bundling

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:11.869Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.869Z
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:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:11.869Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/monorepo.mdc:0-0
Timestamp: 2025-11-24T16:04:11.869Z
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:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T19:09:40.467Z
Learnt from: yamcodes
Repo: yamcodes/arkenv PR: 428
File: apps/playgrounds/bun-solid-start/package.json:10-17
Timestamp: 2025-11-24T19:09:40.467Z
Learning: Applies to apps/playgrounds/bun**/package.json : Bun playgrounds use fixed version strings for workspace packages (e.g., arkenv/vite-plugin, arkenv) instead of the workspace:* protocol because they use Bun as the package manager while the monorepo uses pnpm, and workspace:* protocol doesn't work across different package managers.

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
📚 Learning: 2025-11-24T16:04:19.392Z
Learnt from: CR
Repo: yamcodes/arkenv PR: 0
File: .cursor/rules/pnpm.mdc:0-0
Timestamp: 2025-11-24T16:04:19.392Z
Learning: Applies to package.json : The project uses `pnpm10.20.0` (specified in `packageManager` field)

Applied to files:

  • .github/actions/size-limit/src/size-limit/package.ts
🧬 Code graph analysis (2)
apps/www/bin/build.js (2)
apps/www/bin/postinstall.js (1)
  • child (39-42)
.github/actions/size-limit/src/size-limit/run.ts (1)
  • filter (6-37)
.github/actions/size-limit/src/size-limit/package.ts (3)
.github/actions/size-limit/src/build.ts (1)
  • config (5-70)
.github/actions/size-limit/src/size-limit/run.ts (1)
  • filter (6-37)
.github/actions/size-limit/src/npm/baseline.ts (1)
  • filter (11-139)
⏰ 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). (3)
  • GitHub Check: test-e2e (a11y)
  • GitHub Check: test-e2e (e2e)
  • GitHub Check: test-build (lts/*)
🔇 Additional comments (3)
apps/www/package.json (1)

5-13: Dev script migration to pnpm exec is consistent with workspace usage

Switching the second conc process to pnpm exec next-video sync -w keeps behavior the same while aligning with the repo's pnpm-only tooling and using the locally installed next-video binary from devDependencies.

.github/actions/size-limit/src/size-limit/package.ts (1)

113-176: Bun migration verified—no npm/npx remnants found

The verification confirms the size-limit action has been fully migrated to Bun with no remaining npm or npx usage. The code changes are correct as originally reviewed.

apps/www/bin/build.js (1)

24-36: Build wrapper's switch to pnpm exec matches existing tooling

Routing the requested command through pnpm exec (with args passed through unchanged) is consistent with the monorepo's pnpm usage and mirrors the existing postinstall.js pattern, while preserving NODE_OPTIONS handling and Windows shell behavior.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@yamcodes yamcodes merged commit 93b6e5f into main Nov 24, 2025
14 of 15 checks passed
@yamcodes yamcodes deleted the 432-switch-from-npx-to-pnpm-exec-or-pnpm-dlx-pnpx-wherever-possible branch November 24, 2025 21:42
@coderabbitai coderabbitai bot mentioned this pull request Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github actions Pull requests that update GitHub Actions code www Improvements or additions to arkenv.js.org

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Switch from npx to pnpm exec or pnpm dlx (pnpx) wherever possible

1 participant