Previously, all URLs were rewritten to `index.html` in order to support deep-linking. This works when navigating to URLs that correspond to existing resources. E.g. navigating to `/tutorial` returns `index.html` and then the `DocViewer` takes over and requests `tutorial.json`. Navigating to a non-existent URL (e.g. `/foo`), will return `index.html`, which in turn requests (the non-existent) `foo.json` and throws an error when trying to parse the returned `index.html` as JSON. This commit fixes it by only rewriting URLs that do not request a file (i.e. do not include a `.` in the last path segment). Fixes #15398 |
||
|---|---|---|
| .. | ||
| aio-builds-setup | ||
| content | ||
| e2e | ||
| scripts | ||
| src | ||
| transforms | ||
| .angular-cli.json | ||
| .firebaserc | ||
| .gitignore | ||
| database.rules.json | ||
| firebase.json | ||
| karma.conf.js | ||
| ngsw-manifest.json | ||
| package.json | ||
| protractor.conf.js | ||
| README.md | ||
| tslint.json | ||
| yarn.lock | ||
Site
This project was generated with angular-cli version 1.0.0-beta.26.
Development server
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Code scaffolding
Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.
Build
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Running unit tests
Run ng test to execute the unit tests via Karma.
Running end-to-end tests
Run ng e2e to execute the end-to-end tests via Protractor.
Before running the tests make sure you are serving the app via ng serve.
Deploying to GitHub Pages
Run ng github-pages:deploy to deploy to GitHub Pages.
Further help
To get more help on the angular-cli use ng help or go check out the Angular-CLI README.