You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This only happens using the dev server. Production builds work as expected. This seems to be the same or very similar to issue #762, which was marked as closed.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
Change on src/app/app.module.ts:50: RouterModule.forRoot(ROUTES, { useHash: true })
to RouterModule.forRoot(ROUTES, { useHash: false })
@nekkon, thanks for pointing out the other issue -- I'll close this one as the problem is exactly the same as described there. Using the suggestion on #1056 issue worked for me: "webpack-dev-server": ">=2.1.0-beta.6" seems to break the useHash: false option.
Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass
[X ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
Disabling hash navigation and navigating to any route that is not the root route renders the following
<% if (webpackConfig.htmlElements.headTags) { %> <%= webpackConfig.htmlElements.headTags %> <% } %> Loading... <% if (webpackConfig.metadata.isDevServer && webpackConfig.metadata.HMR !== true) { %> <% } %>
This only happens using the dev server. Production builds work as expected. This seems to be the same or very similar to issue #762, which was marked as closed.
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
Change on src/app/app.module.ts:50:
RouterModule.forRoot(ROUTES, { useHash: true })
to
RouterModule.forRoot(ROUTES, { useHash: false })
Expectation is that we navigate to the correct route (e.g. http://localhost:3000/home)
The text was updated successfully, but these errors were encountered: