You didn't add the options to the TS typings in binding.d.ts. They should get generated after a build as demonstrated by the test.

I wonder why there is no getter in BindingNormalizedOptions . There should be, right?

And you also still need to add it in the actually exported TS definitions in options/output-options.ts and options/normalized-output-options.ts.

@I-Enderlord-I ，hi I don't understand why must add getter in BindingNormalizedOptions and options in options/output-options.ts,can you explain ?

I don't fully understand the project structure myself (thus why I didn't make a pull request), but as far as I see, the typescript files in packages/rolldown define the JS API. Here the binding.d.ts corresponds to the actual objects transfered from the Rust side, while the other files define all kinds of wrappers around that interface.

Specifically, the options/normalized-output-options.ts is basically a one-to-one wrapper of BindingNormalizedOptions in the binding.d.ts and options/output-options.ts defines the OutputOptions interface as it is passed to the user.

As for adding the getter to BindingNormalizedOptions, I have no idea why it was not automatically generated. To me it seems like it should.

I think I get it now... Check out #2987 to see where passing additional properties to the JS/TS API requires changes.

That still leaves receiving more in options/output-options.ts of course...
I guess crates/rolldown_binding/src/options/binding_output_options/mod.rs is the place to add that.

Ok I was correct. See cf09f46 for everything a new options requires.

@I-Enderlord-I THANK YOU SO MUCH

Maybe adding a test to packages/rolldown/tests for this would be nice as well. Just to be sure you got everything and it's actually useable.