Alex Eagle comments

Results 1035 comments of


                                            Alex Eagle

Switch bazel workspace from build_bazel_rules_nodejs to rules_nodejs

We'll maybe do this at the end, if we have buildozer commands that mostly patch up users

Switch bazel workspace from build_bazel_rules_nodejs to rules_nodejs

build_bazel_rules_nodejs has been effectively dead since it wasn't included in 6.0, closing.

Usage report - concatjs

Thanks for keeping such great notes! What is the next step here? Seems like we need to extract some of this into docs, and file issues for the rest? Note...

Usage report - concatjs

I'm not sure what to do, @achew22 do you think we should just transcribe your notes to the wiki or something? I don't want to lose them.

Verify early that test files actually define the corresponding named modules

Sorry everyone - since karma_web_test is no longer in this repo, I'm closing the issue.

Example of next.js build-time prerendering

cc @elliottsj I see you've been down this road before https://github.com/vercel/next.js/issues/9588

Example of next.js build-time prerendering

Nice digging @flolu ! The workaround would be to run without the Bazel sandbox so the files have the original write permissions. But I think we should make a PR...

Example of next.js build-time prerendering

@gregmagolan happens to be working on this for a client, I believe

Address --incompatible_no_rule_outputs_param errors

hmm, I need to check with @c-parsons about how we can switch to the recommend wrapper macro without ruining our docs generation.

ts_library does not work --incremental option (TS 3.5.2)

This is probably blocked on us upgrading google-internal to TS 3.5