Build/update rules ts 0.25.1#28625
Conversation
|
The failures in The failure in the |
|
Maybe we need |
I'll try that out EDIT: It's actually the opposite so that flag is not it. By default, dest is overwritten if it already exists. |
|
|
|
rules_nodejs updated to 0.18.6 in another PR. Rebased this one and this now only updates rules_typescript. |
|
build_206289_step_108_container_0.txt This one shows up 8 times in |
|
In |
|
In |
|
|
|
and |
Updated a spot in the compiler which assumed es5 downlevelling get ready for es2015 devmode in the future.
|
ticket to migrate remaining packages is in https://angular-team.atlassian.net/browse/FW-1061 |
|
@gregmagolan please provide a bit more info in the commit message the next time - this is quite a big change for almost no description of what's going on here. thanks! |
|
this PR doesn't apply cleanly to the patch branch - @gregmagolan can you please send a separate patch-only PR? thanks |
Will do
👍 |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Also brings in changes from #27738 required for the es2015 change.
UPDATE: now at @bazel/typescript and @bazel/karma 0.25.1 which
build_bazel_rules_typescripttonpm_bazel_typescriptandbuild_bazel_rules_karmatonpm_bazel_karmabazelOptions.devmodeTargetOverridetsconfig settings@kyliau I didn't update schematics as you may prefer to wait for the rules_webtesting browser_repositories. Would work with @npm_bazel_karma//:browser_repositories