Packages

@vercel/static-config

3.4.4 · 29 Sep 2026Apache-2.06.5M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 3.x3.4.4No known advisoryLatest line
  • 2.x2.0.17No known advisoryTo 3.4.4
  • 1.x1.0.1No known advisoryTo 3.4.4
  • 0.x0.0.0No known advisoryTo 3.4.4

Latest releases

All 29 releases
  1. 3.x · latest line
  2. 3.4.4

    29 Sep 2026
    • Include ajv's validation error details in the error thrown when the exported config object fails schema validation, so users can see which property is invalid and why instead of a generic "Invalid data" message.

  3. 3.4.3

    26 Aug 2026
    • Lazy-load oxc-parser so a native binding or require(esm) failure falls back to ts-morph instead of crashing config extraction. Load failures are tagged on vc.builder.static_config as static_config.oxc_error:load.

  4. 3.4.2

    26 Aug 2026

Dependency tracking

Know when your own dependencies move

@vercel/static-config published 7 releases in the last 12 months. inlinr folds the routine ones into a line and keeps the few that need 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 19 Nov 2026. Releases and advisories last read 19 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.