build(deps-dev): bump @bazel/typescript from 1.0.0 to 3.7.0

[dependabot-preview]

Bumps @bazel/typescript from 1.0.0 to 3.7.0.

Release notes

Sourced from @​bazel/typescript's releases.

3.7.0

📣 This is likely the last 3.x release of rules_nodejs. We are entering the beta and RC period for 4.0

Upgrade with this WORKSPACE snippet

http_archive(
    name = "build_bazel_rules_nodejs",
    sha256 = "8f5f192ba02319254aaf2cdcca00ec12eaafeb979a80a1e946773c520ae0a2c9",
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/3.7.0/rules_nodejs-3.7.0.tar.gz"],
)

and upgrade your @bazel-scoped npm packages as well.

Features

• builtin: add validate attribute on pkg_npm (5d30c5b), closes #2782
• typescript: support typescript 4.3 (847ef5d)

Bug Fixes

• builtin: don't expose any darwin_arm64 repo or toolchains if not supported by the node version (004da08), closes #2779
• builtin: fix npm_install & yarn_install post_install_patches when symlink_node_modules is enabled (de90747)
• typescript: collect coverage in ts_project (045f91a), closes #2762

3.6.0

Upgrade with

http_archive(
    name = "build_bazel_rules_nodejs",
    sha256 = "0fa2d443571c9e02fcb7363a74ae591bdcce2dd76af8677a95965edf329d778a",
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/3.6.0/rules_nodejs-3.6.0.tar.gz"],
)

and update @bazel-scoped npm packages as well.

Features

major performance improvement: node_modules can now be directories

In every prior release of rules_nodejs, third-party libraries from npm (node_modules) were given generated BUILD files that used a filegroup to expose all the files in the package. Since npm typically has a very high library re-use, it's easy for a project using something like create-react-scripts (or any high-level workflow/build tool) to have tens of thousands of these files. This doesn't work well under Bazel's sandbox or runfiles features, because these do some filesystem operation for every file.

This release adds an add opt-in exports_directories_only mode to yarn_install and npm_install. It defaults to False, but we intend to flip the default to True in our next major release (4.0)

To opt-in, in your WORKSPACE:

npm_install(
    name = "npm",
    ...
    # export only top-level package directory artifacts from node_modules
</tr></table> 

... (truncated)

Changelog

Sourced from @​bazel/typescript's changelog.

3.7.0 (2021-07-02)

Bug Fixes

• builtin: don't expose any darwin_arm64 repo or toolchains if not supported by the node version (004da08), closes #2779
• builtin: fix npm_install & yarn_install post_install_patches when symlink_node_modules is enabled (de90747)
• typescript: collect coverage in ts_project (045f91a), closes #2762

Features

• builtin: add validate attribute on pkg_npm (5d30c5b), closes #2782
• typescript: support typescript 4.3 (847ef5d)

3.6.0 (2021-06-09)

Bug Fixes

• allow for only stderr to be set on npm_package_bin (fa8f5b1)
• builtin: add two missing locations where Mac M1 support needs to be declared (2ad950f), closes #2733
• builtin: propogate tags to both generated targets in generated_file_test (c4403fc)
• builtin: support directory_file_path entry_point in nodejs_binary & nodejs_test when --bazel_patch_module_resolver is set (51676ef)
• jasmine: don't assume entry_point is a label as it may now be a dict (3683466)
• jasmine: unhanded promise rejection causes tests suit to pass (3c4ef58), closes 3.7.0/lib/jasmine.js#L267 #2688
• terser: make terser resolve more robust by not assuming a single /terser/ segment in the path (4709ffb)
• typescript: fixed "output was not created" error for ts_project with supports_workers (807b07b)
• typescript: repair error reporting when a ts_project is missing declaration=True (cd08efe)

Features

• add opt-in exports_directories_only mode to yarn_install and npm_install (defaults to False) (3d182cf)
• support dict style directory_file_path entry_point in nodejs_binary, nodejs_test & jasmine_node_test (737674f)
• support directory_file_path entry_point in npm_umd_bundle (4e44178)

3.5.1 (2021-05-25)

Bug Fixes

• builtin: generated nodejs repository for windows references non-existent file (c1663c5)
• builtin: write stdout/stderr to correct path under chdir (#2681) (36311bb), closes #2680
• esbuild: prefer finding entry_point files in deps rather than srcs (#2692) (dd4c4f3)
• esbuild: provide JSModuleInfo of output bundle (#2685) (233254d)

... (truncated)

Commits

• 22673fc chore: switch buildifier lint to blocklist
• fcf24c2 chore: update to bazel 4.1.0 (#2792)
• 847ef5d feat(typescript): support typescript 4.3
• 045f91a fix(typescript): collect coverage in ts_project
• 39a4401 chore: buildifier
• 07dd8d4 Give reasoning for using ts_project#validate
• e3cdcba chore: update dependency com_github_mattn_go_isatty to v0.0.13
• cd6510e refactor: convert web_testing example to ts_project
• 807b07b fix(typescript): fixed "output was not created" error for ts_project with sup...
• cd08efe fix(typescript): repair error reporting when a ts_project is missing declarat...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by alexeagle, a new releaser for @​bazel/typescript since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes a major update to a development dependency.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)