0.30.0
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 mandatory