François Wouts

That's a good question. These rules weren't designed with this kind of usage in mind, but we might be able to tweak it to allow that. I think @enriched had...

I don't see any issue with this. I've been a bit annoyed by the need to duplicate aliases between the webpack config and `tsconfig.json`, if my understanding is correct this...

I'll take this opportunity to document the history of the decisions that led to the current approach, before discussing your proposal :) ## Approach #1: no `package.json` I actually started...

When I mentioned the issue about an engineer updating a package, I had in mind cases like when upgrading `react` to 16, you also need to upgrade `react-dom` to a...

@enriched That sounds great actually. I think that feature has very high chances of becoming the de facto standard in the future, so leveraging it doesn't seems like a big...

Hi Michael, not exactly. However you may be interested in the discussion happening in https://github.com/zenclabs/bazel-javascript/issues/19. In the above example, how would you specify which exact version of `typescript`, `react` and...

Thanks for reporting. I haven't been able to test on Windows before. A few ideas: - The `--cache-folder` argument is actually a hack that was required to get Yarn running...

It should be using `@nodejs://:yarn`, the priority is consistency across developers of a team. I didn't realise it wasn't the case!

It's indeed not obvious. The key is that `use_default_shell_env` is not set, so the user's default `PATH` is not used. I believe `PATH` is set by `@nodejs//:node`, check out [this...

I think Node and/or Windows' shell might be confused by the `//services/products/server:server_lib` you have in the second argument to `node.cmd`? Maybe double quotes would fix it?