This repository has been archived by the owner on Nov 7, 2020. It is now read-only.
chore(deps): update dependency @bazel/hide-bazel-files to v0.42.3 #299
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.37.0
->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
Renovate configuration
📅 Schedule: "after 10pm every weekday,every weekend,before 5am every weekday" (UTC).
🚦 Automerge: Enabled.
♻️ 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 WhiteSource Renovate. View repository job log here.