Packages

@rollup/browser

4.68.8 · 21 Nov 2026MIT161.1k / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 4.x4.68.8No known advisoryLatest line
  • 3.x3.30.0No known advisoryTo 4.68.8

Latest releases

All 289 releases
  1. 4.68.8

    21 Nov 2026
    • Hoist namespace objects if necessary to avoid broken output

    • Do not try to auto-install source-map-support as it was causing some issues

    • Create namespace objects early when a cycle can read them before their module runs

  2. 4.68.7

    18 Nov 2026
    • Revert previous fix as it was breaking bundling in certain cases

    • Revert previous fix to fail with a parse error instead of exhausting the native stack

  3. 4.68.6

    18 Nov 2026
    • Fail the build with a parse error instead of a native stack overflow for deeply nested expressions

    • Fail with a parse error instead of exhausting the native stack

Dependency tracking

Know when your own dependencies move

@rollup/browser published 65 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 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.