Skip to content

[Feat Request] Support Rolldown Output Option codeSplitting or other ways to build multiple independent library files #594

@voidtan

Description

@voidtan

Describe the regression

Thanks for your works. I'm trying to create multiple library files within the same project, and I expect them to work independently wwithout relying on any other files and without including any import.
I consulted the documentation and attempted to use the new codeSplitting option provided in Rolldown, but my editor tells me this option doesn't exist in rolldownOptions.output.

Reproduction

https://stackblitz.com/edit/vitejs-rolldown-vite-n2d1qpvz

Expected Behavior

The build output consists only of liba.js and libb.js, without any other files. Either liba.js or libb.js contains all required code, so it can run correctly without relying on any other files or using any import statements.

Actual Behavior

The build output includes liba.js, libb.js, and the shared code file dist.js between them.

Steps to Reproduce

Run npm install followd by npm run build

System Info

System
    OS: Linux 5.0 undefined
    CPU: (3)x64 Intel(R) Core(TM) i9-9880H CPU @2.30GHz
    Memory: 0 Bytes/ 0 Bytes
    Shell: 1.0 - /bin/jsh
Binaries:
    Node: 20.19.1 -/usr/local/bin/node
    Yarn: 1.22.19-/usr/local/bin/yarn
    npm:  10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
npmPackages:
    rolldown-vite: 7.3.1 => 7.3.1

Used Package Manager

npm

Logs

No response

Validations

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions