Skip to content

Bump @rolldown/binding-linux-x64-gnu from 1.0.3 to 1.1.0#223

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/rolldown/binding-linux-x64-gnu-1.1.0
Open

Bump @rolldown/binding-linux-x64-gnu from 1.0.3 to 1.1.0#223
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/rolldown/binding-linux-x64-gnu-1.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 17, 2026

Copy link
Copy Markdown
Contributor

Bumps @rolldown/binding-linux-x64-gnu from 1.0.3 to 1.1.0.

Release notes

Sourced from @​rolldown/binding-linux-x64-gnu's releases.

v1.1.0

[!IMPORTANT] This is a minor release. Two changes alter default behavior compared to 1.0.3. Please read this section before upgrading. Everything else is additive (new features, fixes, deps).

⚠️ Notable behavior changes

1. experimental.lazyBarrel is now enabled by default (#9632)

What changed. experimental.lazyBarrel now defaults to true. When a barrel module is recognized as side-effect-free, Rolldown skips compiling the re-exported modules that are never actually used.

Impact. For codebases with large barrel files (component libraries such as Ant Design, @mui/icons-material, etc.) this is a meaningful build-time speedup, and for the vast majority of projects the emitted output is unchanged. In rare cases where a barrel is incorrectly treated as side-effect-free, the optimization could drop a module that was being relied on for its side effects.

How to opt out (backward compatible).

// rolldown.config.js
export default {
  experimental: { lazyBarrel: false },
}

Note: this opt-out flag is planned to be removed in a future release. If you have a case where you must turn it off, please open an issue so we can fix the underlying detection instead.


2. tsconfig project-reference resolution now aligns with TypeScript

Upgrading oxc_resolver (11.19.111.20.0 in #9549, then → 11.21.0 in #9634) changes how Rolldown discovers and resolves tsconfig.json, in particular for a solution-style config (one that only lists references and delegates the real settings to tsconfig.app.json / tsconfig.node.json, as Vite scaffolds), bringing it in line with how TypeScript (tsc / tsserver) itself behaves:

  • Auto-discovery walk-up (oxc-resolver #1154): in auto-discovery mode (tsconfig: true, the default), Rolldown now searches upward from the file's directory and uses the first tsconfig.json that owns the file. A tsconfig.json owns the file when the file matches its files/include/exclude, or when one of its references matches the file. A tsconfig.json that does not own the file is skipped, and the search continues in the parent directory. When no tsconfig.json up the tree owns the file, Rolldown falls back to the outermost (topmost) one found, not the nearest. Previously the nearest tsconfig.json was used unconditionally. This mirrors how TypeScript's tsserver assigns a file to a project.
  • Reference match priority (oxc-resolver #1151): when the root has references, a referenced project that includes the file now takes precedence over the root, instead of the root matching it first (this is what TypeScript already does). So that project's compilerOptions.paths now apply.
  • allowJs (oxc-resolver #1198): whether a .js/.jsx/.mjs/.cjs file is included is now decided by each referenced project's own allowJs, not the root's (again matching TypeScript). So tsconfig.app.json with allowJs: true + paths now resolves aliases for .js files even when the root doesn't set allowJs.

For most projects this is a fix (the standard Vite paths aliases now resolve, closes rolldown/rolldown#8468), but it is a behavior change if you relied on the previous behavior, where the root's paths / allowJs took precedence.

If you relied on the old "root wins" behavior. There is no exact toggle back, because the old behavior was the bug being fixed. The recommended path is to align your config with TypeScript: declare the paths / allowJs on the referenced project that actually owns the files.

If you must keep the old precedence while still using references: a referenced project's match wins, and the first matching references entry takes priority (the root is only a fallback when no reference claims the file). So extract the old root settings into their own config and list it first:

// tsconfig.json (solution root)
{
  "files": [],
  "references": [
    { "path": "./tsconfig.base.json" }, // old root paths/allowJs — listed first, so it wins
    { "path": "./tsconfig.app.json" },
    { "path": "./tsconfig.node.json" }
  ]
}

... (truncated)

Changelog

Sourced from @​rolldown/binding-linux-x64-gnu's changelog.

[1.1.0] - 2026-06-03

🚀 Features

🐛 Bug Fixes

🚜 Refactor

📚 Documentation

  • clarify that RolldownBuild::close method should be called in most cases (#9619) by @​sapphi-red

⚡ Performance

🧪 Testing

⚙️ Miscellaneous Tasks

... (truncated)

Commits
  • c462c7c release: v1.1.0 (#9637)
  • 432bac8 feat: enable experimental.lazyBarrel by default (#9632)
  • 239ca4c feat: import.meta.glob support caseSensitive option (#9594)
  • be8eacc fix(browser): add missing exports and ensure consistency with rolldown pack...
  • 93632ab chore(deps): update dependency vite-plus to v0.1.24 (#9470)
  • b403112 feat: add SOURCEMAP_BROKEN warning for renderChunk hook (#9601)
  • 84b7ed1 feat: add SOURCEMAP_BROKEN warning for transform hook (#9600)
  • 31ad110 perf: avoid unnecessary intermediate sourcemaps (#9599)
  • 5e05eba feat(code-splitting): support group-local includeDependenciesRecursively (#...
  • 4265367 fix(dev): handle the remaining errors in dev (#9570)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@rolldown/binding-linux-x64-gnu](https://github.com/rolldown/rolldown/tree/HEAD/packages/rolldown) from 1.0.3 to 1.1.0.
- [Release notes](https://github.com/rolldown/rolldown/releases)
- [Changelog](https://github.com/rolldown/rolldown/blob/main/CHANGELOG.md)
- [Commits](https://github.com/rolldown/rolldown/commits/v1.1.0/packages/rolldown)

---
updated-dependencies:
- dependency-name: "@rolldown/binding-linux-x64-gnu"
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file npm npm ecosystem dependency updates labels Jun 17, 2026
@dependabot dependabot Bot requested a review from eviltester as a code owner June 17, 2026 03:59
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file npm npm ecosystem dependency updates labels Jun 17, 2026
@greptile-apps

greptile-apps Bot commented Jun 17, 2026

Copy link
Copy Markdown

Greptile Summary

This PR bumps @rolldown/binding-linux-x64-gnu from 1.0.3 to 1.1.0, aligning it with the musl variant that was already at 1.1.0. The change is confined to package.json and the lockfile.

  • Version alignment: The GNU libc and musl variants of the Linux x64 rolldown binding are now both pinned at 1.1.0, eliminating the prior mismatch.
  • Upstream behavior changes in 1.1.0: experimental.lazyBarrel is now enabled by default (skips unused re-exports from side-effect-free barrel files) and tsconfig project-reference resolution now follows TypeScript's own walk-up semantics. Neither change appears to require any config adjustment for this project — no barrel files are relied on for side effects, and the vite config uses direct regex path aliases rather than tsconfig paths.

Confidence Score: 5/5

Safe to merge — only updates a native optional binding to match its sibling variant's version, with no application code changes.

The change is a single optional-dependency version bump in package.json and its corresponding lockfile entry. It corrects a version skew between the two Linux x64 rolldown binding flavors (gnu was behind musl). The 1.1.0 release's behavior changes (lazyBarrel default, tsconfig walk-up) are upstream rolldown internals; the project's vite config uses direct regex aliases rather than tsconfig paths, and there are no barrel-file side-effect patterns that would be affected by lazyBarrel.

No files require special attention.

Important Files Changed

Filename Overview
package.json Bumps @rolldown/binding-linux-x64-gnu from 1.0.3 to 1.1.0, aligning it with the musl variant already at 1.1.0
pnpm-lock.yaml Lockfile updated to record the new 1.1.0 resolution and integrity hash for @rolldown/binding-linux-x64-gnu

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Vite 8.0.16] --> B[rolldown bundler]
    B --> C{Platform binding}
    C -->|Linux x64 glibc| D["@rolldown/binding-linux-x64-gnu\n1.0.3 → 1.1.0"]
    C -->|Linux x64 musl| E["@rolldown/binding-linux-x64-musl\n1.1.0 (unchanged)"]
    D & E --> F[Native Rust build core]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Vite 8.0.16] --> B[rolldown bundler]
    B --> C{Platform binding}
    C -->|Linux x64 glibc| D["@rolldown/binding-linux-x64-gnu\n1.0.3 → 1.1.0"]
    C -->|Linux x64 musl| E["@rolldown/binding-linux-x64-musl\n1.1.0 (unchanged)"]
    D & E --> F[Native Rust build core]
Loading

Reviews (1): Last reviewed commit: "Bump @rolldown/binding-linux-x64-gnu fro..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file npm npm ecosystem dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants