Express_Angular2_Twitter_App
Express_Angular2_Twitter_App copied to clipboard
Manually typing in route or pressing refresh causes 'not found' error
Super helpful article btw, really enjoyed reading it.
When I run your app, it seems manually specifying the route or clicking refresh while on a route will cause the page to redirect to 'not found'.
Do you know why this error is caused? Thanks!
@Syntaf -- thanks for the feedback! Glad to know you found the article useful.
Yeah, I'd noticed that issue with the routing before too. I think it's a combination of how I had to adjust the root url in order to get it to run on Heroku (that first script tag line in the index.html), and also the way that routing used to work in Angular 2.
I know that how routing works in Angular 2 has changed pretty substantially since the time when I wrote this tutorial, though. So that hack that I made would likely not be necessary with more recent versions.