Packages

@mjackson/node-fetch-server

0.7.0 · 6 Jun 2025MIT2.4M / weekRepositoryHomepagenpmAtom feed

Its GitHub repository is archived: no fix will come, so moving off it is strongly recommended.What to use instead
Your version

What to use instead

Its maintainers name no replacement, and the e18e list has none yet.

Latest releases

  1. 0.7.x · latest line
  2. 0.7.0

    6 Jun 2025
    • Add /src to npm package, so "go to definition" goes to the actual source

    • Use one set of types for all built files, instead of separate types for ESM and CJS

    • Build using esbuild directly instead of tsup

  3. 0.6.x · maintenance
  4. 0.6.1

    7 Feb 2025
    • Update typings and docs for http/2 support

  5. 0.6.0

    6 Feb 2025
    • Add http/2 support

Dependency tracking

Know when your own dependencies move

This page watches @mjackson/node-fetch-server. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 21 Nov 2026. Releases and advisories last read 21 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.