Skip to content

[Bug]: rolldown cli options does not work for nested values #9932

Description

@kb019

Reproduction link or steps

Rolldown cli options does not work when values are chained by dot operator.

For example if i do rolldown --config ./rolldown.config.js --generated-code.profiler-names it shows as invalid value

StackBlitz Link

What is expected?

The cli option should be accepted and not throw an an error.

What is actually happening?

Th bug is because cac only converts the top level option to camel case and not the nested values as we can see here

it actually works when i put a camelCase after the dot operator
StackBlitz Link

System Info

System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-13500H
    Memory: 1.79 GB / 15.75 GB
  Binaries:
    Node: 24.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\96110\AppData\Roaming\npm\yarn.CMD
    npm: 11.13.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 11.4.0 - C:\Users\96110\AppData\Local\pnpm\bin\pnpm.CMD
  Browsers:
    Chrome: 149.0.7827.115
    Edge: Chromium (149.0.4022.80)
    Internet Explorer: 11.0.26100.8115
  npmPackages:
    rolldown: workspace:* => 1.1.2

Any additional comments?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    Fields

    Priority

    None yet

    Effort

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions