Sahin Yort

TLDR; the workaround here is to use `--experimental_allow_unresolved_symlinks` to actually symlink. this is due to the limitation of bazel as of today. when two packages depend on each other, bazel...

> What I hadn't noticed before was when running with `--experimental_allow_unresolved_symlinks` is that by the time webpack is being run, the generated `node_modules` structure is littered with broken symlinks. this...

Sorry for the weeks-taking review. I hope this is not blocking you. I have a few concerns about this PR; 1- I am not a huge fan of the synthetic...

Two things that I don't want to continue having. `namespace` and `exporting more than what you have put into your proto` > Of course, we can use types like `type...

Still couldn't spare time to think about this thoroughly. > Maybe we can have inline types and a compiler option to generate and export types like `ReturnType` this is what...

That's weird. i think we can fix it by using the util from https://github.com/aspect-build/bazel-lib/blob/main/lib/windows_utils.bzl. I'll have a look at this. Let's not worry about windows tests failing. Would it be...

@eyouyou I am going to put effort into this week. I made it work with a go server with rollup + typescript on the web.

> I find it hard to believe there's behavior specific to `ibazel run` that wouldn't be the same as `bazel run` - it's just repeating the run more than once...

We've done some work integrating webpack into bazel. That even includes making webpack-devserver work properly under bazel. See #2919 > As far as I know, there is no way to...

Theoretically there should not be any problem. You should be able to use it as you would outside of bazel. We will add examples for widely known plugins eventually.