Update to angular 7.0.4 and latest rules_nodejs

[gregmagolan]

A few issues in the downstream Bazel build that this fixes.

• rules_sass was on an older version that was using load paths that are no longer valid in the newest version. Update to latest version and updated load paths.

• the version of @angular/bazel in package.json (^7.0.3 but pinned to 7.0.3 in the lock file) causes a version skew issue downstream in angular-bazel-example when updating to angular 7.0.4. For the time being, this version needs to be pinned to a specific version that matches the angular http_archive version in WORKSPACE. the exact version match requirement will be relaxed to a range in the future and with Ivy this will no longer be an issue since the downstream Bazel build will use the material bundles

I added a RELEASING.md file to remind the caretaker to match up these versions when releasing

Other updates:

• latest rules_nodejs supports yarn 1.12.1 which is preferred as it support the integrity lock field which is removed from the lock file when yarn_install runs with a pre-1.10 version of yarn

[gregmagolan]

//cc @alexeagle

[devversion]

• The sass_rules are actually based on the latest version. I aligned the API with the //:defs.bzl. See: bazelbuild/rules_sass@8b61ad6
• There is a PR to update to the latest TypeScript and NodeJS rule versions: build: remove windows runfile workaround #14173
• There is a PR for the Angular v7.0.4 update build: update to angular 7.0.4 #14143

The other changes are cool, really like the .md document. Also we should probably coordinate better on changes related to Bazel. There are already various PRs, but those are just awaiting merge and blocked on other stuff.

[jelbourn]

This needs to just be an automatic check in our release script, otherwise it will 100% get broken

[devversion]

I think we should chat about that tools/npm/package.json file. Based on some testing it's just needed because the Angular Bazel rules fall back to @npm for the compiler binaries etc.

RxJS apparently uses their own workspace now, and the comment about why we need this (just for rxjs) is no longer up-to date I think.

[gregmagolan]

It's still needed for rxjs since it uses ts_library in there which depends on the @npm workspace. An rxjs release with a named UMD bundle is in the works (ReactiveX/rxjs#4309). When that lands and makes it into a release then the build can be updated to no longer build RXJS from source.

[jelbourn]

AFAIK this should stay :defs. @devversion?

[devversion]

Yeah, that's the new public API.

[gregmagolan]

You guys are right. It's the downstream repo that is out of date. Thanks.

[gregmagolan]

Looks like everything in here is covered by the other PRs.

Note: (#14173) rules_nodejs 0.16.1 won't work with material but the latest commit will (symlink issue fixed by bazel-contrib/rules_nodejs#422). you can either update to that commit or Alex should tag 0.16.2 shortly. With the rules_nodejs update, the update to yarn 1.10+ is possible as well.

I'll create an issue for the release script update.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}