feat: unifying npm registry requests with caching

[OrbisK]

I think it is not an easy change to refactor all npm requests to useNpmRegistry (yet). As a first step, we could migrate all npm requests to $npmRegistry and $npmApi. Wdyt?

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 3, 2026 11:37am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 3, 2026 11:37am
npmx-lunaria	Ignored		Feb 3, 2026 11:37am

[danielroe]

this looks good!

would you investigate why the browser tests might be failing?

[OrbisK]

this looks good!

would you investigate why the browser tests might be failing?

Working on it. Maybe you know what the issue is. e.g. the org page is broken.

https://npmxdev-git-fork-orbisk-feat-concept-npm-requests-poetry.vercel.app/@nuxt

Here: https://github.com/npmx-dev/npmx.dev/pull/641/changes#diff-93fe589cec6bc2b865b353a91ba90b4407706ff4baf16189a4c2c538351aa26aR523

[OrbisK]

I think the problem is that cachedFetch from the plugin uses the server side fetch on the client 🤷🏽‍♂️

I think I have a fix.

[OrbisK]

I am super confused. Are $npmRegistry request meant to run client side? Because there are cors issues when requesting the orgs

[OrbisK]

Okay. The request returns the data and 200 but cors is still blocking it 🤔

[danielroe]

$npmRegistry should be idempotent, yes. (it should be safe to call in either case)

if there's stale data (or missing data) from the server, then it will refetch on the client

[OrbisK]

Progress: I have fixed it locally. But i am not sure how...

[OrbisK]

@danielroe this line seems to be the problem.

replacing it by a simple mock "fixes" the issue. Any ideas 😅

 const $npmApi = ()=>{
  return Promise.resolve({data: null,})
 }

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request replaces direct NPM registry/API usage with Nuxt-injected runtime helpers ($npmRegistry, $npmApi) wired by a new plugin. Multiple npm-related composables and utilities were updated to call the injected helpers instead of hard-coded constants or useCachedFetch directly. useCachedFetch was modified to merge default fetch options using defu (new dependency). NPM constants were consolidated into shared constants, tests updated to expect relative API paths, and a vitest browser headless flag was made explicit.

Possibly related PRs

• refactor: separate npm composables #827: Touches the same npm composables and utilities and performs related refactoring that moves npm fetches toward shared plugins/helpers.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description directly relates to the changeset, describing the migration of npm requests to $npmRegistry and $npmApi.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[43081j]

caught it up from main for you @OrbisK (lots of conflicts)

code has moved around a fair bit so can you have a read through again to be sure its all good?

[OrbisK]

caught it up from main for you @OrbisK (lots of conflicts)

code has moved around a fair bit so can you have a read through again to be sure its all good?

looks good. 👍🏽 Not sure how to fix the Nuxt instance issue though. I think this might be a Nuxt bug.