After the node resets this should hopefully not be necessary
anymore (we still had an issue this morning but I believe all nodes
that hit the issue also got the fix and if not, I’ll schedule a
targetted clean --expunge). I’ve also added node_modules to
.bazelignore to match the other node_modules directories.
changelog_begin
changelog_end
* Document a more modern way of using IntelliJ with our Bazel project.
Specifically, avoid `bazel-project-view` in favor of excluding a few
slow/unnecessary directories.
CHANGELOG_BEGIN
CHANGELOG_END
* Add .bazel-cache to .bazelignore instead of .bazelproject.
* Bazel: Don't mention a particular version of IntelliJ; just link.
Trust the canonical source.
* added a package.json to work with yarn workspaces
This adds a package.json files on top of our typescript libraries so
that we can develop locally via yarn workspaces. The package.json that
describes the bazel managed dependencies is moved into a subfolder.
CHANGELOG_BEGIN
CHANGELOG_END
* updated bazelignore
* SDK_VERSION -> SDKVERSION
