Alex Eagle

Switch bazel workspace from build_bazel_rules_nodejs to rules_nodejs

2

This is in the Bazel rules style guide, and many rules now ship this way (go and docker are still notable exceptions)

absent c8 package makes tests fail under `bazel coverage`

2

coverage depending on c8, should it be non-fatal? Doesn't work with generated_file_test for example. It could warn somewhere. Maybe only with VERBOSE_COVERAGE. decision: the error message should tell you how...

Needs something legacy in ts_library to be unwired so we can fully switch to package_name

Example of next.js build-time prerendering

17

Next.js docs for prerendering: https://nextjs.org/learn/basics/data-fetching/two-forms

`cd examples/kotlin; bazel test //...` ``` Error in download: java.io.IOException: Error downloading [http://dl.bintray.com/kotlin/kotlinx.html/org/jetbrains/kotlinx/kotlinx-html-js/0.6.12/kotlinx-html-js-0.6.12.jar, https://maven.google.comorg/jetbrains/kotlinx/kotlinx-html-js/0.6.12/kotlinx-html-js-0.6.12.jar, https://repo1.maven.org/maven2org/jetbrains/kotlinx/kotlinx-html-js/0.6.12/kotlinx-html-js-0.6.12.jar] to /home/alexeagle/.cache/bazel/_bazel_alexeagle/b8bc351f100be5cce4ff637306da72b7/external/org_jetbrains_kotlinx_kotlinx_html_js_0_6_12/file/downloaded: GET returned 404 Not Found ``` Last time I tried to resolve this...

TypeScript has the behavior that if you run `tsc a.ts` and `a.ts` contains an import from `./b.ts`, then that module is automatically included in the program and emitted. This means...

Allow import paths to be workspace-relative

3

In https://github.com/bazelbuild/rules_typescript/issues/77 we let you `import {} from 'my_wksp/src/some_file'` but in some existing codebases there's an assumption that TypeScript is configured such that you can `import {} from 'src/some_file'` rather...

reduce dependence on browser tests

1

For the most part, we don't really care about having a real browser for our integration tests. `domino` DOM is good enough to test our bundles in nodejs. I tried...

we do `bazel run @fine_grained_deps_yarn//typescript/bin:tsc` in our CI. starting with Bazel 2.0, this program discovers all the inputs from some other workspace it seems, and fails after a long time...

they are basically no-op tests for removed injector feature