build: bump @bazel/typescript from 2.3.2 to 3.2.1

[dependabot]

Bumps @bazel/typescript from 2.3.2 to 3.2.1.

Release notes

Sourced from @​bazel/typescript's releases.

3.2.1

upgrade with

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

and update your @bazel-scoped npm dependencies.

Bug Fixes

• remove --keep-names (4a26898)
• update node versions map (#2484) (9506fe0)
• esbuild: add --preserve-symlinks flag by default (eb71285)
• esbuild: add link_workspace_root for workspace absolute imports (#2476) (ba7e48e), closes #2474
• use ':' instead of '=' for esbuild 'define' argument (#2469) (b0fddae)
• use ':' instead of '=' for esbuild 'external' argument (#2475) (bc7dc82)

Features

• add generate_local_modules_build_files flag to yarn_install and npm_install rules (#2449) (a6449b7)
• typescript: add data attribute (ac2097c)

3.2.0

Upgrade with:

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

and update your @bazel-scoped npm dependencies to match.

Features

multi-linker

Previously we restricted a given Node program under Bazel to get all dependencies from a single node_modules tree, which in practice meant that all monorepo dependencies had to go in the root package.json file. This is now fixed! A target can depend on multiple, so long as the package_path attribute is set on yarn_install/npm_install in the WORKSPACE. (2c2cc6e)

@bazel/esbuild

... (truncated)

Changelog

Sourced from @​bazel/typescript's changelog.

3.2.1 (2021-02-23)

Bug Fixes

• remove --keep-names (4a26898)
• update node versions map (#2484) (9506fe0)
• esbuild: add --preserve-symlinks flag by default (eb71285)
• esbuild: add link_workspace_root for workspace absolute imports (#2476) (ba7e48e), closes #2474
• use ':' instead of '=' for esbuild 'define' argument (#2469) (b0fddae)
• use ':' instead of '=' for esbuild 'external' argument (#2475) (bc7dc82)

Features

• add generate_local_modules_build_files flag to yarn_install and npm_install rules (#2449) (a6449b7)
• typescript: add data attribute (ac2097c)

3.2.0 (2021-02-13)

Bug Fixes

• multi-linker linking when only output files in sandbox (ebb9481)
• builtin: fix coverage source file paths (ae4ec78)
• docs: fix formatting of nodejs_binary#chdir (1caced8)
• docs: fix regex that replaces //packages with @​bazel (c31c0b6)
• docs: version selector shows 3.x (38f4f78)
• typescript: allow up to typescript 4.2, add tests for 3.7-4.1 (ea168a7)
• typescript: fixed build for external ts_project targets (c89e0aa)
• version number not edited after release candidate (ac2bb62)

Features

• add esbuild package (e7e5286)
• builtin: add coverage all: true support (8386b97)
• support for nested node_modules in linker (2c2cc6e)

3.1.0 (2021-02-02)

Bug Fixes

• forward srcs, deps and visibility of dummy_bzl_library to the filegroup when publishing (0466084)
• linker fix for invalid symlink creation path in createSymlinkAndPreserveContents (14086a8)

... (truncated)

Commits

• ac2097c feat(typescript): add data attribute
• c89e0aa fix(typescript): fixed build for external ts_project targets
• 2c2cc6e feat: support for nested node_modules in linker
• ea168a7 fix(typescript): allow up to typescript 4.2, add tests for 3.7-4.1
• 99bfe5f feat(typescript): create a better ts_project worker (#2416)
• 9d7827b fix(typescript): capture js files in outputs of ts_project if allow_js
• 1dda0af docs(typescript): add host configuration to rootDirs (#2401)
• 142bd75 docs: fix broken and misplaced links in Typescript docs
• c2927af refactor(builtin): remove node_modules attribute from nodejs_binary, nodejs_t...
• ea34460 chore: cleanup flag settings which are now redundant with the default
• Additional commits viewable in compare view

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 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]

The following labels could not be found: area: build, merge ready, merge safe, target: patch.

[dependabot]

Superseded by #30.