Bump @bazel/karma from 0.33.1 to 0.39.1

[dependabot-preview]

Bumps @bazel/karma from 0.33.1 to 0.39.1.

Release notes

Sourced from @bazel/karma's releases.

0.39.1

Update:

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

and run yarn upgrade --scope @bazel to update all your @bazel scoped npm packages to the latest versions.
(or manually do the npm equivalent - they don't have a way to update a scope)

Bug Fixes

• fix for bazelbuild/rules_nodejs#1307 (7163571)
• karma: load scripts in strict mode (5498f93), closes #922

Features

• examples: demonstrate using Webpack to build and serve a React app (c5d0909)

0.39.0

Update:

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

and run yarn upgrade --scope @bazel to update all your @bazel scoped npm packages to the latest versions.
(or manually do the npm equivalent - they don't have a way to update a scope)

Cool stuff

Programs which dynamically require packages such as plugins now run correctly under npm_package_bin. For example, we can now run Jest under Bazel and it can resolve the jest-babel plugin.

We are getting closer to a state where nearly all npm packages run under Bazel. The remaining issues are some handling of symlinks, where the program doesn't have a --preserveSymlinks option or doesn't adhere to it in all places.

Bug Fixes

• bundle names in angular examples (b4f01e2)
• builtin: allow more than 2 segments in linker module names (7e98089)
• webpack should be a peerDep of @bazel/labs (312aa4d)

... (truncated)

Changelog

Sourced from @bazel/karma's changelog.

0.39.1 (2019-10-29)

Bug Fixes

• fix for bazelbuild/rules_nodejs#1307 (7163571)
• karma: load scripts in strict mode (5498f93), closes #922

Features

• examples: demonstrate using Webpack to build and serve a React app (c5d0909)

0.39.0 (2019-10-23)

Bug Fixes

• bundle names in angular examples (b4f01e2)
• builtin: allow more than 2 segments in linker module names (7e98089)
• webpack should be a peerDep of @bazel/labs (312aa4d)

Code Refactoring

• remove dynamic_deps feature (#1276) (b916d61)

Features

• builtin: turn off a strict requirement for peer dependencies (#1163) (bd2f108)
• examples: add Jest example (#1274) (f864462), closes /github-redirect.dependabot.com/ecosia/bazel_rules_nodejs_contrib/issues/4#issuecomment-475291612

BREAKING CHANGES

• The dynamic_deps attribute of yarn_install and npm_install is removed,
  in favor of declaring needed packages in the deps/data of the rule that
  invokes the tool.

0.38.3 (2019-10-11)

Bug Fixes

• terser: terser_minified should support .mjs files when running on directory (#1264) (6b09b51)

... (truncated)

Commits

• 5498f93 fix(karma): load scripts in strict mode
• 35b3276 test: move /e2e/karma_* tests to /packages/karma/test (#1269)
• 3d1ec33 refactor: all providers exported from //:providers.bzl (#1263)
• bb1f9b4 feat(typescript): add JSNamedModuleInfo provider to ts_library outputs (#1215)
• 4e86283 fix: pin @bazel/karma karma dep to ~4.1.0 as 4.2.0 breaks stack traces in kar...
• 7e3e6be refactor: add index.bzl
• 86c616c chore: rename rules_karma_dependencies
• cefc2ae chore: cleanup some deprecated APIs (#1160)
• 646d75b build: update to rules_webtesting 0.3.3 (#1143)
• 12d9d96 refactor: replace usages of expand_path_into_runfiles to _to_manifest_path (#...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @bazel/karma 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 an out-of-range 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @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 your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• 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)

[dependabot-preview]

Superseded by #42.