Performance fix: remove globs

Builds should now be faster because Bazel doesn't need to scan directories during the analysis phase. Previously we created BUILD files under the Bazel-managed dependencies when using yarn_install that contained glob
https://docs.bazel.build/versions/master/be/functions.html#glob

Note the new included_files option to yarn_install https://bazelbuild.github.io/rules_nodejs/npm_install/npm_install.html#yarn_install which lets you further trim the files needed as inputs to Bazel actions.

BREAKING CHANGE:

• yarn_install and npm_install no longer generate "lite" targets like @npm//node_modules/glob:glob__lite

yarn cache

Should improve performance of repository rule yarn_install by using the global yarn cache on your machine.

0.15.0

BREAKING CHANGES:

• Fine grained deps targets changed from @wksp//:pkg to @wksp//pkg and binary targets changed from @wksp//:pkg/name to @wksp//pkg/bin:name

0.14.0

Various bug fixes including Windows support for rollup.

BREAKING CHANGES:

• If your nodejs_binary relies on variables from bazel build --define=foo=bar to be available as environment variables in the node process, you must now list those variable names in the configuration_env_vars attribute
• The manual_build_file_contents attribute on yarn_install and npm_install is now appended to generated build file instead of replacing its contents
• The prod_only attribute on yarn_install was removed since fine-grained npm deps gives more control

0.13.1

Minor bugfix to jasmine spec filtering.

See https://github.com/bazelbuild/rules_nodejs/wiki#migrating-to-rules_nodejs-013 for breaking changes in 0.13

fine-grained deps

This release has a major breaking change, see
https://github.com/bazelbuild/rules_nodejs/wiki#migrating-to-rules_nodejs-013

0.2.3: Change node module load order

Try looking in the directory containing the label first, before the one in the working directory.
Needed for tsickle tests to use a different TypeScript version in one test, and probably generally useful.