build(deps-dev): bump the npm-development group across 1 directory with 2 updates

[dependabot]

Bumps the npm-development group with 2 updates in the / directory: @vercel/ncc and vitest.

Updates @vercel/ncc from 0.38.4 to 0.44.0

Release notes

Sourced from @​vercel/ncc's releases.

0.44.0

0.44.0 (2026-06-09)

Features

• read permissions pr.yml (#1323) (5ea625e)

0.43.0

0.43.0 (2026-06-09)

Changes

• BREAKING CHANGE: add Node 24 and 26 support, remove 20 (#1318) (#1305)
• switch npm releases to trusted publishing (OIDC) (#1325) (#1327) (#1328) (#1329) (#1330) (#1331) (#1332)
• switch package management to pnpm (#1321)
• fix predictable global cache directory in /tmp enables symlink/hijack risks (#1314)
• reorder extension resolution to prioritise TypeScript over JSON (#1315)
• support TypeScript 6 transpile builds (#1316)

Commits

• 88be21f chore(deps): Bump actions/checkout from 5 to 6 (#1300)
• 5ea625e feat: read permissions pr.yml (#1323)
• a1ff315 feat: remove npm devDependency (#1332)
• 9e077ab feat: add publishConfig to package.json (#1331)
• 7290aa7 feat(ci): upgrade python and remove LLVM LTO flags from MSVC build to fix Nod...
• a428a10 feat: publish using node@24 (#1329)
• 3192116 feat: use canonical package repository metadata (#1328)
• 4461a52 feat: lock semantic-release publish dependencies (#1327)
• e00b2de feat: switch npm releases to trusted publishing (OIDC) (#1325)
• 5f8f509 feat: delete .github/CODEOWNERS (#1324)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vercel/ncc since your current version.

Updates vitest from 4.1.5 to 4.1.8

Release notes

Sourced from vitest's releases.

v4.1.8

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple ids [backport to v4]  -  by @​toxik and @​Zelys-DFKH in vitest-dev/vitest#10474 (675b4)

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

• runner: Limit concurrency per task branch in addition to per leaf callbacks (backport)  -  by @​hi-ogawa in vitest-dev/vitest#10384 (4f0f2)

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

• browser: Provide project reference in ToMatchScreenshotResolvePath  -  by @​macarie and @​sheremet-va in vitest-dev/vitest#10138 (31882)
• Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options  -  by @​hi-ogawa, Codex and @​sheremet-va in vitest-dev/vitest#10196 (2847d)
• browser: Simplify orchestrator otel carrier  -  by @​hi-ogawa in vitest-dev/vitest#10285 (18af9)

   🏎 Performance

• Stringify diff objects only once  -  by @​sheremet-va in vitest-dev/vitest#10276 (9f7b1)

    View changes on GitHub

Commits

• e61f2dd chore: release v4.1.8
• e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
• a09d472 chore: release v4.1.7
• a8fd24c chore: release v4.1.6
• 18af98c fix(browser): simplify orchestrator otel carrier (#10285)
• 3188260 feat(browser): provide project reference in ToMatchScreenshotResolvePath (#...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

React Compiler Report

Commit: eac84535c2

3 files scanned · 2 compiled · 3 issues

File	Component	Reason
failing.tsx:6	ConditionalHook	Error Hooks must always be called in a consistent order, and may not be called conditionally.
failing.tsx:15	RefMutation	Error Cannot access refs during render
failing.tsx:16	RefMutation	Error Cannot access refs during render

Fix with AI

Fix the following React Compiler issues. The compiler reported these because they violate the Rules of React.

Rules:
- Do not add useMemo, useCallback, or React.memo. The compiler handles memoization once the code follows the rules.
- Do not change the underlying logic or behavior of any component.
- If a fix requires restructuring, extract helper functions rather than rewriting the component.

File: failing.tsx
  - ConditionalHook (line 6): Hooks must always be called in a consistent order, and may not be called conditionally. See the Rules of Hooks (https://react.dev/warnings/invalid-hook-call-warning)
  - RefMutation (line 15): Cannot access refs during render
    React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
  - RefMutation (line 16): Cannot access refs during render
    React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)

1 function opted out of compilation

• opted-out.tsx:2 useCustomHook (use no memo)