build: update to latest aspect_bazel_lib, aspect_rules_js, aspect_rules_jasmine and aspect_rules_esbuild

[gregmagolan]

There is a regression with worker mode in this release of rules_ts for Node 14 (works fine with Node 16) I disabled it in the ts_project targets in the PR. Sahin is working on a fix for Node 14 worker mode but the ts_project targets in the repository are small so worker mode doesn't add much anyway.

The latest version of rules_js will keep your pnpm-lock.yaml files up-to-date automatically (when your source-of-truth is a yarn.lock file) when any of the inputs to the npm_translate_lock repository rule change. The .aspect/rules/external_repository_action_cache/npm_translate_lock_* files act like an action cache to know when to re-run pnpm import to update the pnpm lock files.

UPDATE: Node 14 worker mode issue is now fixed in rules_ts 1.3.2 (with rules_js 1.20.3 transitive dep)

[gregmagolan]

I also recommend setting ASPECT_RULES_JS_FROZEN_PNPM_LOCK on CI so that if the pnpm lock file is out of date you'll get a red build. https://docs.aspect.build/rules/aspect_rules_js/docs/pnpm#update_pnpm_lock

[devversion]

@gregmagolan is there a link for the regression so we can know when to remove the worker disabling?

[gregmagolan]

@gregmagolan is there a link for the regression so we can know when to remove the worker disabling?

Fix is underway: aspect-build/rules_js#927

[gregmagolan]

ts_project worker mode re-enabled with the latest rules_js & rules_ts releases cut this morning. I also greened up the other CI failure. This should be clear to land now

[devversion]

@gregmagolan I have a conflict-resolved version of your PR, along with the environment variable: #1873

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}