Open klemenoslaj opened 5 years ago
Status: docs team will need to work with engineering to create more complex examples ensuring that we explain the pertinent points.
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
π Docs or angular.io bug report
Description
There is already a pretty good documentation in regards to Angular CLI Builders, however, I get stuck right after trying something more complex than triggering a simple command.
I am extending the existing
@angular-devkit/build-ng-packagr
builder, so that certain logic is executed after the packagr builder is done. That all works fine, however I don't know how to test it correctly.I tried to create a fake workspace, where I would run my builder, but obviously that fails due to absence of dependencies, like
@angular/core
.I as well tried to look into official builder itself where I found that bunch of deprecated API is used, therefore did not proceed there.
π¬ Minimal Reproduction
What's the affected URL?**
https://next.angular.io/guide/cli-builder
Reproduction Steps**
command-builder
yarn test
This can of course be fixed by creating
package.json
and installing@angular/core
in the fake workspace, but is this the right way?π₯ Exception or Error