diff --git a/docs/rules.md b/docs/rules.md
index 7ce700e..b41315a 100755
--- a/docs/rules.md
+++ b/docs/rules.md
@@ -10,8 +10,8 @@ Users should not load files under "/internal"
## webpack_bundle
-webpack_bundle(name, args, deps, entry_point, entry_points, output_dir, srcs, supports_workers,
- webpack, webpack_config, webpack_worker)
+webpack_bundle(name, args, data, deps, entry_point, entry_points, output_dir, srcs,
+ supports_workers, webpack, webpack_config, webpack_worker)
Runs the webpack-cli under bazel.
@@ -23,6 +23,7 @@ Runs the webpack-cli under bazel.
| :------------- | :------------- | :------------- | :------------- | :------------- |
| name | A unique name for this target. | Name | required | |
| args | Command line arguments to pass to Webpack.
These argument passed on the command line before arguments that are added by the rule. Run bazel with --subcommands to see what Webpack CLI command line was invoked.
See the [Webpack CLI docs](https://webpack.js.org/api/cli/) for a complete list of supported arguments. | List of strings | optional | [] |
+| data | Runtime dependencies to include in binaries/tests that depend on this target.
The transitive npm dependencies, transitive sources, default outputs and runfiles of targets in the data attribute are added to the runfiles of this taregt. Thery should appear in the '*.runfiles' area of any executable which has a runtime dependency on this target.
If this list contains linked npm packages, npm package store targets or other targets that provide JsInfo, NpmPackageStoreInfo providers are gathered from JsInfo. This is done directly from npm_package_stores and transitive_npm_package_stores fields of these and for linked npm package targets, from the underlying npm_package_store target(s) that back the links via npm_linked_packages and transitive_npm_linked_packages.
Gathered NpmPackageStoreInfo providers are used downstream as direct dependencies when linking a downstream npm_package target with npm_link_package. | List of labels | optional | [] |
| deps | Runtime dependencies which may be loaded during compliation. | List of labels | optional | [] |
| entry_point | The point or points where to start the application bundling process.
See https://webpack.js.org/concepts/entry-points/ | Label | optional | None |
| entry_points | - | Dictionary: Label -> String | optional | {} |
@@ -40,7 +41,8 @@ Runs the webpack-cli under bazel.
webpack_dev_server_rule(name, chdir, data, enable_runfiles, entry_point, env, expected_exit_code,
- log_level, node_options, patch_node_fs, srcs, webpack_config)
+ include_declarations, include_npm_linked_packages, include_transitive_sources,
+ log_level, node_options, patch_node_fs, webpack_config)
@@ -57,10 +59,12 @@ webpack_dev_server_rule(name, entry_point | Internal use only | Label | required | |
| env | Environment variables of the action.
Subject to $(location) and make variable expansion. | Dictionary: String -> String | optional | {} |
| expected_exit_code | The expected exit code.
Can be used to write tests that are expected to fail. | Integer | optional | 0 |
+| include_declarations | When True, declarations and transitive_declarations from JsInfo providers in data targets are included in the runfiles of the target.
Defaults to false since declarations are generally not needed at runtime and introducing them could slow down developer round trip time due to having to generate typings on source file changes. | Boolean | optional | False |
+| include_npm_linked_packages | When True, files in npm_linked_packages and transitive_npm_linked_packages from JsInfo providers in data targets are included in the runfiles of the target.
transitive_files from NpmPackageStoreInfo providers in data targets are also included in the runfiles of the target. | Boolean | optional | True |
+| include_transitive_sources | When True, transitive_sources from JsInfo providers in data targets are included in the runfiles of the target. | Boolean | optional | True |
| log_level | Set the logging level.
Log from are written to stderr. They will be supressed on success when running as the tool of a js_run_binary when silent_on_success is True. In that case, they will be shown only on a build failure along with the stdout & stderr of the node tool being run. | String | optional | "error" |
| node_options | Options to pass to the node.
https://nodejs.org/api/cli.html | List of strings | optional | [] |
| patch_node_fs | Patch the to Node.js fs API (https://nodejs.org/api/fs.html) for this node program to prevent the program from following symlinks out of the execroot, runfiles and the sandbox.
When enabled, js_binary patches the Node.js sync and async fs API functions lstat, readlink, realpath, readdir and opendir so that the node program being run cannot resolve symlinks out of the execroot and the runfiles tree. When in the sandbox, these patches prevent the program being run from resolving symlinks out of the sandbox.
When disabled, node programs can leave the execroot, runfiles and sandbox by following symlinks which can lead to non-hermetic behavior. | Boolean | optional | True |
-| srcs | JavaScript source files from the workspace. | List of labels | optional | [] |
| webpack_config | Webpack configuration file.
See https://webpack.js.org/configuration/ | Label | optional | None |
diff --git a/scripts/mirror_releases.sh b/scripts/mirror_releases.sh
index 16c581f..e4710f0 100755
--- a/scripts/mirror_releases.sh
+++ b/scripts/mirror_releases.sh
@@ -11,28 +11,41 @@ npx pnpm install webpack@5.72.1 webpack-cli webpack-dev-server @bazel/worker --l
touch BUILD
cat >WORKSPACE <