Skip to content

Support PathLocationStrategy "HTML5 Mode" Routing #172

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

Closed
btford opened this issue Feb 3, 2016 · 3 comments
Closed

Support PathLocationStrategy "HTML5 Mode" Routing #172

btford opened this issue Feb 3, 2016 · 3 comments

Comments

@btford
Copy link
Contributor

btford commented Feb 3, 2016

Ideally, we'd have a catch-all route on the development server to load index.html when we can't map to a file-system resource.

@intellix
Copy link
Contributor

intellix commented Feb 3, 2016

Fixed and merged already in: #121

@filipesilva
Copy link
Contributor

The catch-all route is not in, I believe.

EDIT: I tested on latest master and it seems to be fine, as @intellix mentioned. @btford can you reproduce on the latest master? If so, feel free to reopen.

clydin pushed a commit that referenced this issue Jun 5, 2018
To avoid people going in those directories and running npm install.

Fixes #172.
hansl added a commit that referenced this issue Jun 6, 2018
To avoid people going in those directories and running npm install.

Fixes #172.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants