Skip to content

chore: refresh all dependencies - #26

Merged
Brooooooklyn merged 4 commits into
mainfrom
chore/refresh-all-deps
Aug 17, 2026
Merged

chore: refresh all dependencies#26
Brooooooklyn merged 4 commits into
mainfrom
chore/refresh-all-deps

Conversation

@Brooooooklyn

Copy link
Copy Markdown
Member

Refresh all dependencies: npm, Cargo, and GitHub CI actions.

npm / yarn

  • Bump all devDependencies to latest: ava 6→8, typescript 5→7, chalk 5→6, lint-staged 16→17, npm-run-all2 8→9, oxlint 1.8→1.78, prettier 3.6→3.9, @napi-rs/cli 3.0→3.8.6, @emnapi/* 1.4→1.11, @oxc-node/core 0.0.35→0.1.0, @tybys/wasm-util 0.10.0→0.10.3, tinybench 6.0→6.1
  • Yarn 4.12.0 → 4.18.0 (4.12's built-in compat/typescript patch crashes on TS 7, which no longer ships lib/_tsc.js)
  • AVA 8: extensions config changed from object to array

Cargo

  • napi 3.0.0 → 3.12.1
  • napi-derive 3.0.0 → 3.6.3
  • tokio 1.40.0 → 1.53.1
  • napi-build 2 → 2.4.1

GitHub CI actions

  • actions/checkout v6 → v7
  • actions/setup-node v6 → v7
  • actions/cache v4 → v6
  • actions/upload-artifact v5 → v7
  • actions/download-artifact v6 → v8
  • cross-platform-actions/action v0.30.0 → v1.4.0 (migrated to the v1.x pattern: separate VM-start step + build step with shell: cpa.sh {0}, since the run param is deprecated)
  • FreeBSD 14.2 → 15.1 (latest stable)

Generated files

  • index.js / index.d.ts regenerated via napi build
  • yarn.lock re-resolved

- npm: bump all devDependencies to latest (ava 8, typescript 7,
  oxlint 1.78, lint-staged 17, npm-run-all2 9, chalk 6, etc.)
- yarn: 4.12.0 -> 4.18.0 (4.12's compat/typescript patch breaks on TS7)
- ava 8: extensions config object -> array
- cargo: napi 3.12.1, napi-derive 3.6.3, tokio 1.53.1, napi-build 2.4.1
- CI: checkout/setup-node v7, cache v6, upload-artifact v7,
  download-artifact v8, cross-platform-actions v1.4.0 (cpa.sh shell pattern),
  FreeBSD 14.2 -> 15.1
- regenerate index.js / index.d.ts via napi build

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: efcd7ad0c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
@napi-rs/cli 3.8.6's WASI build flow requires the 'emnapi' package
(declared as an optional peer dep, so not auto-installed) and its
libemnapi-napi-rs-mt.a archive must export emnapi_create_env /
emnapi_delete_env, which only exists in emnapi 2.x.

- add emnapi 2.0.0-alpha.4 (pinned, per CLI's exact version-match check)
- bump @emnapi/core and @emnapi/runtime to 2.0.0-alpha.4 to match
- regenerate WASI wrappers (callback-demo.wasi.cjs, callback-demo.wasi-browser.js,
  wasi-worker*.mjs, callback-demo.wasi.d.cts) with napi build
- gitignore *.wasm build artifacts
- AVA 8 requires Node ^22.20 || ^24.12 || >=26 (its emittery dep uses
  iterator helpers), so drop node@20 from the test matrices in favor of
  node@22 and node@24
- add @napi-rs/wasm-runtime as a direct devDependency: the root-level
  WASI wrappers (callback-demo.wasi.cjs, wasi-worker*.mjs) require it,
  but as a transitive dep of wasm32-conditional packages yarn's
  node-modules linker only nests it, so it is unresolvable from the root
- use NAPI_RS_FORCE_WASI=true (the new tri-state loader only treats
  'true'/'error' as force; '1' falls back to native first)
@Brooooooklyn
Brooooooklyn merged commit 29f6872 into main Aug 17, 2026
34 checks passed
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.

1 participant