I just posted about recent changes we made in the Bazel JavaScript layer. It's easier to migrate now that you can continue running whatever tools with the same config as Maven is doing. For example, if the `ts_library` rule doesn't work for you, it's possible to just use `tsc` (with the caveat as you point out, it will be slower)
https://dev.to/jakeherringbone/layering-in-bazel-for-web-389...
That, combined with Maven->Bazel being a common migration path for Java project, should mean that your costs to change are incremental.
Another benefit for large projects is test execution time. If you can parallelize all your testing on a farm of machines you can bring your CI time down by an order of magnitude.
That, combined with Maven->Bazel being a common migration path for Java project, should mean that your costs to change are incremental.
Another benefit for large projects is test execution time. If you can parallelize all your testing on a farm of machines you can bring your CI time down by an order of magnitude.