-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Closed
Labels
P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulImpacts a large percentage of users; if a workaround exists it is partial or overly painfuleffort1: easy (hours)type: bug/fix
Description
- OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
any - Versions. Please run
ng --version. If there's nothing outputted, please run in a Terminal:
any - Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
The app was fully created with the angular-cli - The log given by the failure. Normally this include a stack trace and some
more information.
Error 404 - Mention any other details that might be useful.
I have an Angular 2 App deployed via GitHub Pages (using the CLI) here, whether you refresh the page or navigate using deep linking it does not work and an Error 404 from GitHub is given. I have used the CLI to generate the routes and used the new router (not therouter-deprecated).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulImpacts a large percentage of users; if a workaround exists it is partial or overly painfuleffort1: easy (hours)type: bug/fix