Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: publish ts-api-guardian rule in the npm package #29977

Closed
wants to merge 2 commits into from
Closed

build: publish ts-api-guardian rule in the npm package #29977

wants to merge 2 commits into from

Conversation

alan-agius4
Copy link
Contributor

With this change downstream users will no longer need to build ts-api-guardian from source as now the bazel rule is available in the npm package.

This can be used by installing ts-api-guardian as a devDependency and changing the load syntax from:

load("@angular//tools/ts-api-guardian:index.bzl", "ts_api_guardian_test")

to:

load("@npm_ts_api_guardian//:index.bzl", "ts_api_guardian_test")

Note: downstream users should also clean their WORKSPACE and remove the dependencies of angular workspace.

@alan-agius4 alan-agius4 added area: build & ci Related the build and CI infrastructure of the project target: major This PR is targeted for the next major release labels Apr 18, 2019
@ngbot ngbot bot added this to the needsTriage milestone Apr 18, 2019
@alan-agius4 alan-agius4 marked this pull request as ready for review April 18, 2019 18:04
@alan-agius4 alan-agius4 requested a review from a team as a code owner April 18, 2019 18:04
@alan-agius4 alan-agius4 changed the title build: published ts-api-guardian rule in the npm package build: publish ts-api-guardian rule in the npm package Apr 18, 2019
With this change downstream users will no longer need to build ts-api-guardian from source as now the bazel rule is available in the npm package.

This can be used by installing ts-api-guardian as a devDependency and changing the load syntax from:
```
load("@angular//tools/ts-api-guardian:index.bzl", "ts_api_guardian_test")
```

to:
```
load("@npm_ts_api_guardian//:index.bzl", "ts_api_guardian_test")
```

**Note**: downstream users should also clean their `WORKSPACE` and remove the dependencies of angular workspace.
tools/ts-api-guardian/BUILD.bazel Outdated Show resolved Hide resolved
@alexeagle
Copy link
Contributor

I assume you found a way to test it downstream

@alan-agius4
Copy link
Contributor Author

Yeah I did, with the good old npm link

@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Apr 19, 2019
@benlesh benlesh closed this in d7f7826 Apr 19, 2019
@alan-agius4 alan-agius4 deleted the ts-api-guardian-bazel-rule branch April 20, 2019 05:15
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
With this change downstream users will no longer need to build ts-api-guardian from source as now the bazel rule is available in the npm package.

This can be used by installing ts-api-guardian as a devDependency and changing the load syntax from:
```
load("@angular//tools/ts-api-guardian:index.bzl", "ts_api_guardian_test")
```

to:
```
load("@npm_ts_api_guardian//:index.bzl", "ts_api_guardian_test")
```

**Note**: downstream users should also clean their `WORKSPACE` and remove the dependencies of angular workspace.

PR Close angular#29977
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants