Open aptenodytes-forsteri opened 5 days ago
Thanks for the good repro. I think this is fixed in the latest rules_ts release though, mainly just as a side-effect of adding declarations_transpiler
and no_emit
features. Can you try it out?
Yes, 3.2.0 seems to fix it. Worth adding a test case for this if there isn't one already? I'll also check to see if any other combinations of ts and js can break it.
If you can contribute a test case that failed previously that would be great. I don't think any were added when fixed but maybe you can verify that?
My test case now passes with the new version, but a subsequent dependency fails
emit_transpiler_js = emit_js and transpiler and transpiler != "tsc"
I think this is now getting set to false, so when I try to esbuild from my generated js, I get no js file exists.
I guess maybe I need to eliminate emit_declaration_only = True,
Err no, when I delete emit_declaration_only = True
, I get the conflict again.
Updated repro case here: https://github.com/aptenodytes-forsteri/ts_js_interop/blob/main/src/BUILD.bazel
Can you try adding test cases to rules_ts to reproduce it?
Can you try adding test cases to rules_ts to reproduce it?
If I remove emit_declaration_only = True, I get the conflict error again.
What happened?
When importing js into ts while also transpiling with swc, rules_ts produces an error.
Repro case here: https://github.com/aptenodytes-forsteri/ts_js_interop
Version
Development (host) and target OS/architectures: Ubuntu 22.04
Output of
bazel --version
: bazel 7.3.2Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:Language(s) and/or frameworks involved: js / ts
How to reproduce
Any other information?
No response