Skip to content

Bump @rolldown/binding-linux-x64-musl from 1.0.0 to 1.1.0#175

Merged
eviltester merged 1 commit into
masterfrom
dependabot/npm_and_yarn/rolldown/binding-linux-x64-musl-1.0.3
Jun 11, 2026
Merged

Bump @rolldown/binding-linux-x64-musl from 1.0.0 to 1.1.0#175
eviltester merged 1 commit into
masterfrom
dependabot/npm_and_yarn/rolldown/binding-linux-x64-musl-1.0.3

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps @rolldown/binding-linux-x64-musl from 1.0.0 to 1.1.0.

Release notes

Sourced from @​rolldown/binding-linux-x64-musl'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-musl'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 dependabot Bot added dependencies Pull requests that update a dependency file npm npm ecosystem dependency updates labels Jun 10, 2026
@dependabot dependabot Bot requested a review from eviltester as a code owner June 10, 2026 03:59
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file npm npm ecosystem dependency updates labels Jun 10, 2026
@greptile-apps

greptile-apps Bot commented Jun 10, 2026

Copy link
Copy Markdown

Greptile Summary

This dependabot PR bumps @rolldown/binding-linux-x64-musl (the musl/Alpine Linux native binding for the Rolldown bundler) from 1.0.0 to 1.1.0. The lock file is cleaned up accordingly, removing now-unused 1.0.0 package entries.

  • Notable behavior change in 1.1.0: experimental.lazyBarrel is now enabled by default, which skips compiling unused re-exports from barrel modules. For the rare case where a barrel is incorrectly treated as side-effect-free, this could silently drop a module relied on for side effects; it can be disabled via experimental: { lazyBarrel: false } in the rolldown config.
  • tsconfig resolution change: oxc_resolver was upgraded to align tsconfig project-reference discovery with TypeScript's own behavior — this fixes standard Vite paths aliases but is a breaking change for any code that relied on root-wins precedence in solution-style configs.

Confidence Score: 5/5

Safe to merge — this is a routine dependabot bump of an optional native binding used only on musl-based Linux hosts.

The change is limited to one optional dependency version in package.json and the corresponding lock file cleanup. The 1.1.0 release notes document two notable behavior changes (lazyBarrel default flip and tsconfig resolution walk-up), but both only affect musl/Alpine build environments and have clear opt-outs. No application logic is touched.

No files require special attention.

Important Files Changed

Filename Overview
package.json Bumps @rolldown/binding-linux-x64-musl optional dependency from 1.0.0 to 1.1.0; @rolldown/binding-linux-x64-gnu remains at 1.0.3, leaving the two Linux platform bindings on different minor versions.
pnpm-lock.yaml Lock file updated to reflect the musl binding version bump and clean up stale 1.0.0 entries for both gnu and musl packages.

Reviews (3): Last reviewed commit: "Bump @rolldown/binding-linux-x64-musl fr..." | Re-trigger Greptile

@dependabot dependabot Bot changed the title Bump @rolldown/binding-linux-x64-musl from 1.0.0 to 1.0.3 Bump @rolldown/binding-linux-x64-musl from 1.0.0 to 1.1.0 Jun 11, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/rolldown/binding-linux-x64-musl-1.0.3 branch from 54173a4 to 22a944e Compare June 11, 2026 09:30
Bumps [@rolldown/binding-linux-x64-musl](https://github.com/rolldown/rolldown/tree/HEAD/packages/rolldown) from 1.0.0 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-musl"
  dependency-version: 1.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/rolldown/binding-linux-x64-musl-1.0.3 branch from 22a944e to 688e466 Compare June 11, 2026 09:41
@eviltester eviltester merged commit b78e355 into master Jun 11, 2026
11 checks passed
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/rolldown/binding-linux-x64-musl-1.0.3 branch June 11, 2026 09:45
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.

1 participant