meta: specify architecture

[ovflowd]

This PR tightens the architecture for dependencies to be wasm whenever possible.

npm install --cpu wasm32 --os wasip1-threads

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
api-docs-tooling	Ready	Preview	Feb 18, 2026 4:33pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.62%. Comparing base (32a824c) to head (795b1f6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #614   +/-   ##
=======================================
  Coverage   78.62%   78.62%           
=======================================
  Files         128      128           
  Lines       12461    12461           
  Branches      902      902           
=======================================
  Hits         9798     9798           
  Misses       2658     2658           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

orama-db Generator

File	Base	Head	Diff
orama-db.json	8.03 MB	8.03 MB	-1.78 KB (-0.02%)

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• npm-shrinkwrap.json: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The PR description states "This PR tightens the architecture for dependencies to be wasm whenever possible," but the actual changes in this file are about modifying peer dependency flags in the npm lockfile, which has no relation to WebAssembly (wasm) architecture.

The changes involve:

• Removing "peer": true from packages like @noble/hashes, @orama packages, csstype, scheduler, and zod-to-json-schema
• Adding "peer": true to packages like @typescript-eslint/parser, acorn, eslint-plugin-jsdoc, postcss, preact, and vite

These modifications affect npm's dependency resolution strategy but are unrelated to wasm. The project already uses wasm packages (lightningcss-wasm, @minify-html/wasm) which are not being changed. Either the PR description is incorrect, or these changes were committed to the wrong PR.

[Copilot]

The acorn package is listed as a direct dependency in package.json (line 52) but is being marked with "peer": true in the lockfile. In npm lockfile v3 format, the "peer": true flag indicates a package is installed only to satisfy peer dependency requirements, not as a direct dependency. This conflict could cause acorn to not be installed properly, leading to runtime errors when the code tries to import it. The same issue exists for other packages marked as peer despite being direct dependencies.

Suggested change

"peer": true,

[Copilot]

The preact package is listed as a direct dependency in package.json (line 64) but is being marked with "peer": true in the lockfile. In npm lockfile v3 format, the "peer": true flag indicates a package is installed only to satisfy peer dependency requirements, not as a direct dependency. This conflict could cause preact to not be installed properly, leading to runtime errors when the code tries to import it. Preact is used directly in the codebase for rendering components, so it must be installed as a direct dependency.

Suggested change

"peer": true,

[avivkeller]

Looking over the diff, the lock file didn’t actually add a dependency :-/. I’ll look into the other dynamic importing approach I mentionex