What is the current behavior?
As of #308 the TypeScript version and integrity can be automatically extracted, however this misses out on functionality present in npm_translate_lock such as applying patches.
A recent TypeScript release included a bug microsoft/TypeScript#57849 (5.4.x, broken in 5.4.2 and fixed in 5.4.5) which was fixed with a trivial patch, however it could not be applied to Rules TS's @npm_typescript repo.
Describe the feature
Instead of pulling in TypeScript with bespoke logic
|
http_archive_version = repository_rule( |
support using TypeScript from npm_translate_lock's node_modules directly. This way functionality like patching comes free.
What is the current behavior?
As of #308 the TypeScript version and integrity can be automatically extracted, however this misses out on functionality present in
npm_translate_locksuch as applying patches.A recent TypeScript release included a bug microsoft/TypeScript#57849 (
5.4.x, broken in5.4.2and fixed in5.4.5) which was fixed with a trivial patch, however it could not be applied to Rules TS's@npm_typescriptrepo.Describe the feature
Instead of pulling in TypeScript with bespoke logic
rules_ts/ts/private/npm_repositories.bzl
Line 66 in 87e3723
support using TypeScript from
npm_translate_lock'snode_modulesdirectly. This way functionality like patching comes free.