Update dependency build_bazel_rules_nodejs to v0.42.3 #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3.1
->0.42.3
Release Notes
bazelbuild/rules_nodejs
v0.42.3
Compare Source
To upgrade:
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
Features
v0.42.2
Compare Source
Bug Fixes
v0.42.1
Compare Source
To upgrade:
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)
New stuff
In 0.41.0 we noted that a feature for inserting
<script>
and<link>
tags was dropped fromts_devserver
andpkg_web
but the replacement wasn't available. Now it is thanks to @jbedard who published a standalone npm packagehtml-insert-assets
. You can see how it's wired in the examples.If you waited to upgrade before, now you should.
Bug Fixes
BREAKING CHANGES
npm_package_bin
and all rules generated by it, to match genrule behavior as documented at https://docs.bazel.build/versions/master/be/make-variables.html#predefined_genrule_variablesThis means that usage of the
$@​
shortcut to refer to the output directory should now be$(@​D)
whenoutput_dir=True
and you can now use
$@​
to refer to the location of a single outputv0.42.0
Compare Source
This release had a bug, see 0.42.1 instead
https://github.com/bazelbuild/rules_nodejs/releases/tag/0.42.1
v0.41.0
Compare Source
To upgrade:
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)
BREAKING CHANGES
As mentioned before, we are close to a 1.0 release, so we are making all our breaking changes now to prepare for a period of stability. Sorry for the long list this time!
web_package
rule has been renamed topkg_web
and is now a public APIUpdate your load statements from
to
ts_devserver
andpkg_web
(previouslyweb_package
) no longer have anindex_html
attribute.They expect an index.html file to be among the assets, and to already
have the script and link tags needed for the app to work.
The feature where those tags were injected into the html dynamically has
been moved to its own rule, inject_html.
We are in a transition state where the
inject_html
rule is not published, because we want this to be a plain npm package and not Bazel-specific. We will publish this functionality soon. If you depend on it, you may want to delay this upgrade.internal/rollup_bundle rule is removed. see https://github.com/bazelbuild/rules_nodejs/wiki for migration instructions
Removed the expand_location_into_runfiles helper from //internal:node.bzl
Load it from //internal/common:expand_into_runfiles instead
npm karma deps for karma_web_test and karma_web_suite are now peer deps so that the versions used can be chosen by the user.
This PR also removes the built-in
@io_bazel_rules_webtesting//browsers/sauce:chrome-win10
saucelabs support. It is not very useful as it only tests a single browser and it difficult to use. In the angular repo, saucelabs support was implemented with a custom karma config using karma_web_test. This is the recommended approach.--define=DEBUG=1
is no longer functional to request debugging outputs. Use-c dbg
instead (this matches Bazel's behavior for C++).We renamed some of the generated targets in the
@nodejs//
workspace:bazel run @​nodejs//:npm
is replaced withbazel run @​nodejs//:npm_node_repositories
andbazel run @​nodejs//:yarn
is replaced withbazel run @​nodejs//:yarn_node_repositories
.@nodejs//:yarn
and@nodejs//:npm
now run yarn & npm in the current working directory instead of on all of thepackage.json
files innode_repositories()
.@nodejs//:bin/node
&@nodejs//:bin/node.cmd
(on Windows) are no longer valid targets. Use@nodejs//:node
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/node
.@nodejs//:bin/yarn
&@nodejs//:bin/yarn.cmd
(on Windows) are no longer valid targets. Use@nodejs//:yarn
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/yarn
.@nodejs//:bin/npm
&@nodejs//:bin/npm.cmd
(on Windows) are no longer valid targets. Use@nodejs//:npm
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/npm
.Bug Fixes
chore
Code Refactoring
Features
v0.40.0
Compare Source
Bug Fixes
Features
args
attribute to support additional command line arguments (563bad7)0.39.1 (2019-10-29)
Bug Fixes
Features
v0.39.1
Compare Source
Bug Fixes
Features
v0.39.0
Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
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
Features
0.38.2 (2019-10-09)
Bug Fixes
Features
0.38.1 (2019-10-03)
Bug Fixes
Features
v0.38.3
Compare Source
Bug Fixes
Features
v0.38.2
Compare Source
Bug Fixes
Features
v0.38.1
Compare Source
Bug Fixes
Features
v0.38.0
Compare Source
Bug Fixes
chore
Code Refactoring
Features
BREAKING CHANGES
index.bzl instead.
The @yarn workspace is no longer created. Use @nodejs//:yarn instead.
To use them, first install the http-server and/or history-server packages
Then load("@npm//http-server:index.bzl", "http_server")
(or replace with history-server, noting that the rule has underscore where the package has hyphen)
0.37.1 (2019-09-16)
Bug Fixes
Features
v0.37.1
Compare Source
Bug Fixes
Features
v0.37.0
Compare Source
Bug Fixes
chore
Features
BREAKING CHANGES
0.36.2 (2019-08-30)
Bug Fixes
Features
0.36.1 (2019-08-20)
Features
v0.36.2
Compare Source
Bug Fixes
Features
v0.36.1
Compare Source
Features
v0.36.0
Compare Source
Bug Fixes
Features
jasmine_config
(715ffc6)v0.35.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
jasmine: You can no longer get jasmine_node_test from @build_bazel_rules_nodejs.
Use
load("@​npm_bazel_jasmine//:index.bzl", "jasmine_node_test")
instead
You need to remove
@npm//jasmine
from the deps of thejasmine_node_test
If you use user-managed dependencies, see the commit for examples of
the change needed
Also makes the repo bazel-lint-clean, so running yarn bazel:lint-fix no
longer makes edits.
v0.34.0
Compare Source
Bug Fixes
Features
0.33.1 (2019-07-12)
Bug Fixes
v0.33.1
Compare Source
Bug Fixes
v0.33.0
Compare Source
Bug Fixes
Features
0.32.2 (2019-06-21)
Bug Fixes
0.32.1 (2019-06-19)
Bug Fixes
v0.32.2
Compare Source
Bug Fixes
v0.32.1
Compare Source
Bug Fixes
v0.32.0
Compare Source
Bug Fixes
Features
v0.31.1
Compare Source
jasmine_node_test
macro now passestemplated_args
through tonodejs_test
BREAKING CHANGES:
@bazel/typescript
restricted an API return type which breaksngc-wrapped
like so:TypeError: digests.entries(...) is not a function or its return value is not iterable
Update to
@angular/[email protected]
to pick up the fix (when Angular 8.0.1 is released, the fix will be there too)-preserve-symlinks-main
flag is now set along with--preserve-symlinks
flag when node version is 10.2.0 or greater. If using avendored_node
version older than 10.2.0, you must specify thenode_version
you are using so that this flag is not set. Setting the flag on an older version of node will lead to an error.The
entry_point
attribute ofnodejs_binary
,nodejs_test
androllup_bundle
has been changed to a label from a string.Updating your BUILD files should be trivial in most cases.
For example:
would become either,
or
if using relative or absolute label syntax respectively.
If the
entry_point
was referencing a.js
file that is the output of a ts_library rule then you now must point theentry_point
to the corresponding.ts
and the affected rules will use the corresponding.js
output.For example:
becomes,
For more information and examples see https://bazelbuild.github.io/rules_nodejs/node/node.html#nodejs_binary.entry_point and https://bazelbuild.github.io/rules_nodejs/rollup/rollup_bundle.html#rollup_bundle.entry_point.
v0.30.2
Compare Source
New
@bazel/create
package simplifies the quickstart experience.Just
yarn create @​bazel
ornpm init @​bazel
to create a Bazel + JavaScript workspace.Other changes
@bazel/buildozer
package. This is a program and Go library for machine-editing BUILD.bazel files, and we plan to use it to automate migrations when we make breaking changes in the future.npm_install
crash where Bazel reports a target cycle, looks likeEXPAND_TEST_SUITES com.google.devtools.build.lib.pkgcache.TestFilter@e17a1
@bazel/bazel
no longer warns about running from a global installv0.30.1
Compare Source
v0.30.0
Compare Source
BREAKING CHANGES:
We depend on Bazel 0.26 which has a new "managed directories" feature. This was added specifically to improve the integration with external package managers npm and yarn.
we now use the same node_modules directory under Bazel as your package manager does when run locally.
See https://github.com/bazelbuild/rules_nodejs/wiki#migrating-to-rules_nodejs-030 for migration instructions.
yarn_install
&npm_install
attributeexcluded_packages
is now deprecated. Now that yarn_install and npm_install use node_modules in the user's folder by default, this attribute is no longer useful since large packages such as@bazel/bazel
will no longer be installed twice.yarn_install
&npm_install
attributedata
is no longer needed, unless you'vesymlink_node_modules = False
. This is because Bazel runs the package manager in your project directory so all files are available without explicit declaration.npm_install#package_lock_json
attribute is now mandatoryv0.29.2
Compare Source
Add a terser compile-time constant for Angular
v0.29.1
Compare Source
Version bumps for dependencies
Remove the extra yarn_install needed by the
web_package
rulev0.29.0
Compare Source
BREAKING CHANGES
ts_library
strict dependencies now apply to libraries from npm.You can use
deps=["@​npm//:node_modules"]
to depend on all node_modules, but this has performance implications.We suggest adding missing dependencies individually to the
deps
of thets_library
, following guidance from the compile errors.Changes
New
check_bazel_version_range
function to ensure your team uses the Bazel version you requireWe automatically generate a named UMD bundle at
@npm//node_modules/package:package.umd.js
so that the concatjs bundler can work with third-party libraries.ts_library
now automatically gathers typings from npm packages in thedeps
.web_package
ts_devserver
, fix for #728rollup_bundle
v0.28.0
Compare Source
BREAKING CHANGES
npm_package
now throws for any files insrcs
which do not reside in the same package as the target. These files should be in thedeps
instead. (Note that in previous releases, we didn't permit these files in deps.)Features
rollup_bundle
: new output_group lets you select .js and .js.map files together for different output flavors, thanks @jbedardrollup_bundle
: UMD bundles can now be requested es5 and es5 minified, thanks @jbedardFixes
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.