Alex Eagle
Alex Eagle
This is hard to observe in rules_python because our example is contrived: https://github.com/bazelbuild/rules_python/blob/main/examples/wheel/BUILD.bazel#L132 has the `pytest` dependency, but we don't have any `requirements` file saying this library has such a...
I don't think that satisfies this FR, no. It's interesting if every service in a monorepo maintains a requirements.in file. But 1) many orgs have chosen "single dependency closure at...
Figured it out. I was using 0.4.1 on the command line, but had copied in 0.3 from the example on the Installation page.
Ping @pcj in case you don't check new issues in this repo very often.
Yeah, I agree with that, but it's unfortunate that program behavior changes when run under Bazel. Will make it harder to get wide-scale adoption. I'm glad you didn't encounter that...
We just made a change to Angular, such that the closure compiler compat layer (`tsickle`) is not required for `@angular/compiler-cli`. We attempt to require it, and if found, then we...
I'm bumping into this again in https://github.com/bazelbuild/rules_typescript/pull/398
I think we are settling on `bazelDynamicDependencies` We would like to use `dynamicDependencies` but maybe npm will decide that has a meaning in the future?
FWIW, rules_nodejs now has `npm_install` and `yarn_install` rules that let you defer the package management to Bazel, and just do your first `bazel build` with no install step first. On...
@vicb is working on this for angular/angular