-
Notifications
You must be signed in to change notification settings - Fork 516
Angular2 doesn't seem to be working client side when publishing with VS Code #338
Comments
Thanks for the quick reply, Mark. That's what I thought initially and that's why I tried disabling/enabling. I experienced this issue on both my Mac and PC when I cloned the repository. "dotnet run" from the command prompt/terminal gave me the same result. On the PC, I ran the same files in the same browser from Visual Studio 2015 with no problems. Not sure what could be the issue. |
In most cases, VS Code is just a text editor and doesn't influence how your application runs. If you've set up some custom If that's not it, I'd need more information (ideally, repro steps) otherwise I'm not sure how it would be possible to proceed with diagnosing this. Sorry! |
@levarcooper So potentially you might need to run |
For me it was due to the environment variable not being set to 'Development' and webpack-dev-server fails to serve the in-memory script files. Set environment explicitly to Development For VsCode try launching as sudo/administrator. More info and options here #302 |
I also think recent updates Steve made look they might make the default ENV Development, so things like this don't happen. |
@MarkPieszak That was the problem. I ran |
I downloaded it yesterday and I was having issues with that until I set the environment to development. |
I'm running the ANGULAR2SPA app in VS Code and everything seems to be working fine with the exception of the following:
When I run the application from VS 2015 Professional, everything works perfectly. I disabled javascript in my browser and it works exactly as it did with "dotnet run" and VS Code. I checked the browser to make sure vendor.js was loaded. Is there anything in VS Code that would prevent would prevent javascript from running? Obviously I'm just working from VS 2015 but I use VS Code when working on a Mac so I wanted to know if anyone else experienced similar issues.
The text was updated successfully, but these errors were encountered: