I had a similar problem with the same file. In my case, I have a complex application that is being developed in stages. I installed the Angular seed in a subdirectory. Due to my file structure, when I start npm start
, the server on which the server is running has poor relative link locations. For example, in the screenshot below, you will see that the application is trying to find style.css
in http: // localhost: 3000 / medface / RecordWriter / styles.css ; however, it should look at http: // localhost: 3000 / styles.css , since the root of the web server created by npm start
is in / medface / RecordWriter /.

As for your project. The key to detecting a problem with your link is opening the developer panel and checking the actual network request. If you share screenshots, we can help you better understand your copy.
What worked for me
In my case, I reconfigured my local web server to handle any non-reserved pages in the Angular2 folder and returned the index instead. When I start npm start
, I close the open browser page and use my regular web server. Instead of viewing my application on localhost: 3000, I am viewing the application at localhost / medface / RecordWriter / (which is equivalent to localhost: 80 / medface / RecordWriter ).
The immediate side of my temporary approach is that the page should be updated before changes occur, but it reliably and reliably loads all resources and allows my Angular2 code to work along with some old code base in other areas of the website that have not been converted to Angular2 . Regardless, this may work for you.
source share