Alex Eagle
Alex Eagle
We don't have the resources to maintain the persistent worker code, and we're turning it off by default in 2.0. Closing as infeasible.
filegroup srcs are a critical design flaw here. thinking about a simpler approach.
@gregmagolan and I don't remember the context of this one. It looks like our goal was to permit `sass` source files to ts_project, but I don't see an issue filed...
For case 1, I'd expect you to get this error: https://github.com/aspect-build/rules_swc/commit/245f582ee0abab5aacf6c32ed18ed5578d6d05ba#diff-1444361579758fc6be4458b5105b2ee3ee623d72154094c3fa1fd9056845903eR75 saying that you need an out_dir to get swc to do .js->.js
Yup, agreed about the use case, it's reasonable and important. The most practical answer is to give different filenames somehow. For example `src/foo.jsx -> bazel-bin/foo.js` or `src/foo.js -> bazel-bin/foo.{mjs,cjs}`. Then...
It's over a year old, our last comment was about a documentation change, and I don't have a current repro. Closing and will let someone report again if we still...
@thesayyn any idea if this looks fixable this week?
Still noticing that rules_ts has no windows coverage on BCR :(
Due to bugs like this one, we are moving away from supporting the Persistent Worker in the next major 2.0 release of rules_ts, and likely will never fix this, sorry!
Due to bugs like this one, we are moving away from supporting the Persistent Worker in the next major 2.0 release of rules_ts, and likely will never fix this, sorry!