Alex Eagle

Obviously the other problem is that skylib wasn't accepting contributions for many months, so like other users we had to fork.

As far as I know, there is no way to configure webpack's built-in file watcher to avoid it noticing files getting unlinked (deleted) while Bazel is updating the bazel-out tree....

@diceride you might be confused by layering - this project doesn't make any decisions about how NodeJS works. We merely mirror their semantics into Bazel rules. Same for TypeScript. So...

CI failure ``` error TS18003: No inputs were found in config file 'C:/b/makknmlb/execroot/build_bazel_rules_nodejs/packages/typescript/test/ts_project/esm/tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '[]'. ``` is probably because of Windows lack...

Note: https://github.com/bazelbuild/rules_nodejs/pull/3405 seems like the prerequisite but needs someone with some time to green it up...

Hey, sorry no one looked at your PR! > suggest to 1. cd . sure, it could do something clever for that case

hi sorry, we've been 100% heads-down on the 5.x breaking changes and getting that release out. I doubt this is fixed there but we should at least verify it's still...

FWIW, @gregmagolan used this toolchain (from a Mac host) with Engflow RBE yesterday and got a correct nodejs interpreter on the exec platform, so I don't think this is totally...

We are working on distributing the go binaries so there's no Go/gazelle dependency exposed to users. Starting with puller/pusher

No, sorry no tracking issues, and after starting the investigation I'm not sure cutting our rules_go or bazel_gazelle dependencies would work very well. That was a bit off-topic here anyhow......