---
title: "@rolldown/debug 1.3.3: release notes, upgrades and advisories"
description: "@rolldown/debug 1.3.3: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/@rolldown/debug
lang: en
---

[Packages](https://inlinr.com/packages)

# @rolldown/debug

1.3.3 · 18 Nov 2026 MIT 312.2k / week [Repository](https://github.com/rolldown/rolldown) [Homepage](https://rolldown.rs/) [npm](https://www.npmjs.com/package/@rolldown/debug) [Atom feed](https://inlinr.com/packages/feed/@rolldown/debug)

Your version 

## Latest releases

[All 38 releases](https://inlinr.com/packages/@rolldown/debug/releases)

1. ### [1.3.3](https://inlinr.com/packages/@rolldown/debug/releases/1.3.3 "Open this release") [](https://github.com/rolldown/rolldown/releases/tag/v1.3.3 "Read this release where it was published")  
18 Nov 2026

  - Show plugin timings as a table
  - Reset plugin module options when modules are fetched again
  - Prevent UMD dependencies from using host AMD loaders
2. ### [1.3.2](https://inlinr.com/packages/@rolldown/debug/releases/1.3.2 "Open this release") [](https://github.com/rolldown/rolldown/releases/tag/v1.3.2 "Read this release where it was published")  
11 Nov 2026

  - Removed  
  Drop no-op init calls from re-exports and imports
  - **magic-string:** Add a `hires` constructor option
  - **cjs:** Provide `__dirname` and `__filename` to CommonJS modules in Node ESM output
3. ### [1.3.1](https://inlinr.com/packages/@rolldown/debug/releases/1.3.1 "Open this release") [](https://github.com/rolldown/rolldown/releases/tag/v1.3.1 "Read this release where it was published")  
9 Nov 2026

  - **inline-common-chunks:** Inline chunks using `import.meta.ROLLDOWN_FILE_URL_*`
  - **cli:** Apply --environment before loading the binding
  - **rolldown\_plugin\_vite\_resolve:** Escape module names in generated error stubs

Dependency tracking

## Know when your own dependencies move

@rolldown/debug shipped a new major in the last 12 months, among 38 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

- 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](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/@rolldown/debug/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

## Same family

- [@rolldown/pluginutils 245.6M/wk](https://inlinr.com/packages/@rolldown/pluginutils)
- [rolldown 181.7M/wk](https://inlinr.com/packages/rolldown)
- [@rolldown/plugin-babel 10.2M/wk](https://inlinr.com/packages/@rolldown/plugin-babel)
- [@rolldown/perf-kit 50.3k/wk](https://inlinr.com/packages/@rolldown/perf-kit)

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](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
