fix(bazel): specify the package and lock files using the workspace

[alan-agius4]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• [] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?
When used downstream (CLI), The following error is being thrown

no such package '@ts-api-guardian_runtime_deps//': Unable to load package for //tools/ts-api-guardian:package.json: not found. and referenced by '//etc/api:angular_devkit_schematics_tasks_api'

no such package 'tools/ts-api-guardian': BUILD file not found on package path and referenced by '//etc/api:angular_devkit_schematics_testing_api.accept'

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

//cc @alexeagle

[alan-agius4]

Thanks @alexeagle!

…

On Fri, 07 Sep 2018 at 16:38, Alex Eagle ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In tools/ts-api-guardian/index.bzl <#25694 (comment)>: > @@ -17,14 +17,12 @@ ***@***.***_bazel_rules_nodejs//internal/node:node.bzl", "nodejs_binary", "nodejs_test") -COMMON_MODULE_IDENTIFIERS = ["angular", "jasmine", "protractor"] I went ahead and made the change so we can get this greened up — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25694 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQv-Wq_EFhrs2sX7CZtIGZ-ldxzbL5nFks5uYoT9gaJpZM4WO8Km> .

[IgorMinar]

This PR doesn't apply cleanly to the patch branch. @alan-agius4 can you send a separate PR for that branch please?

[alan-agius4]

Yeah I can do that tomorrow. Most likely it will have to contain the changes of the following PR as well #25690 as it was merged only to master.

…

On Fri, 07 Sep 2018 at 22:51, Igor Minar ***@***.***> wrote: This PR doesn't apply cleanly to the patch branch. @alan-agius4 <https://github.com/alan-agius4> can you send a separate PR for that branch please? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#25694 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQv-WhQnsu23ptaRimRdxHrDxyGQPwjjks5uYtxjgaJpZM4WO8Km> .

[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.}