-
Notifications
You must be signed in to change notification settings - Fork 5
Angular devkit/architect cli #1
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
Angular devkit/architect cli #1
Conversation
...unks as non initial in dev-server
... cleaning output directory before emitting
... chunks in stats output
...tic dependency requests
...ailable in unit tests
... Webpack resolver
... to access file emitters
...` syntax when `webWorkerTsConfig` is not defined in karma builder
...ion target in test configuration
... file system cache
...nfigurations from browser builder
...ation forms for static properties
...Script configuration loading
...build optimizer usage
...PropertyAccessFromIndexSignature` to workspace tsconfig
...ker implementation supports Node.js 12.14"
...ptimizer for global styles
...EsVersionForFileName` helper
...bination to optimize global scripts
...downlevelled in third-party libraries
...oints when marking async chunks
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!
and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
i️ Googlers: Go here for more info.
No description provided.