Andrew Scott
cabca2d93f
There were a myriad of problems when using the type: 'cli' for a tutorial: * Editor component would flicker the non-cli version first since that was the default value. Fixed by not showing anything until type is available * Editor component still rendered a split screen when there was no preview. Fixed * Project initialization was incorrect because the terminal would appear to be available but really didn't work until dependencies were done installing. Fixed by sharing initialization with regular project init and piping the install output to the interactive terminal * Terminals would not work when going from type: 'cli' to another or vice versa. This is because the element instance of a terminal cannot change once it is opened. Fixed by dispoing and recreating terminals when the element changes PR Close #61246
Angular.dev
This site is built with Angular.
The content is written primarily in Markdown format located in src/content. For simple edits, you can directly edit the file on GitHub and generate a Pull Request.
Local Development
For local development, yarn is the preferred package manager. You can set up a local environment with the following commands :
# Clone Angular repo
git clone https://github.com/angular/angular.git
# Navigate to project directory
cd angular
# Install dependencies
yarn
# Build and run local dev server
# NOTE: Initial build will take some time
yarn docs
If you are having issues with the docs building, see the FAQs section.
Contributing
Want to report a bug, contribute some code, or improve the documentation? Excellent!
Read through our contributing guidelines to learn about our submission process, coding rules, and more.
And if you're new, check out one of our issues labeled as help wanted or good first issue.
Code of Conduct
Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.
FAQs
The build is failing and I'm seeing bazel:bazel failed: missing input file messages.
This is most likely due to a bazel dependency / caching issue. To resolve this, run the following command:
# Try this first
yarn bazel clean
# If that doesn't work, try it with the expunge flag
yarn bazel clean --expunge