-
Notifications
You must be signed in to change notification settings - Fork 18
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
issue when running start:dll #125
Comments
Do you have the complete error stack trace? |
I tried again from scratch, it has the same error. Here is the full log: /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js run start:dll
APP_ENV is not set in your .env, it will default to "development"
�]0;webpack-dashboard��]0;webpack-dashboard��[?1049h�[?1h�=�[1;1r�[?25l�[1;1H�[H�[2J�[?1000h�[?1002h�[?1003h�[?1005h |
My OS is MacOS Sierra 10.12.3 |
sorry but cannot reproduce it, maybe you can create a repo for demo |
Is webpack-dev-server used to debug the ts files? If it is, is there any other ways to run the app on webpack-dev-server without webpack-dashboard? Or is there any other way to debug the ts files? What I need is just to find a way to debug the ts files in the browser. Thank you! |
Of course you can run it without webpack-dashboard, just modify the start script to
You should able to debug using Chrome developer tools |
Hi, I had tried that before I asked you, it did not work. Port 8080 is binded, but I got the following when accessing localhost:8080 via Chrome.
Here is the log: /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js run start
APP_ENV is not set in your .env, it will default to "development" [at-loader] Using typescript@2.1.6 from typescript and "tsconfig.json" from /Users/yuan/Documents/angular-webpack-starter-master/tsconfig.json. (node:798) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see webpack/loader-utils#56 [at-loader] Checking started in a separate process... [at-loader] Ok, 0.687 sec. [at-loader] Checking started in a separate process... [at-loader] Ok, 0.002 sec. |
then can you choose another port? or close the program using the port |
What I meant was that the port 8080 was bound after I run that command. So the server was started, but the content was not loaded. Sorry for the misunderstanding. |
But it works on latest snapshot, did you try on latest snapshot of the starter? |
Yes, I downloaded the zip directly from Github, and the angular version is 2.4.7 |
Do you have modified the code or it's fresh clone? I just tried to remove yarn.lock and try to rebuild the yarn cache, but still working, so it's not starter/package issue. Most likely, you've another program that use 8080 port too, and it collided |
I did not modify anything. |
then it's weird, I just tried and nothing wrong happened... I can only suspect the port problem |
closing as no actionable, and not starter issue. please reopen if still having this with reproducable. Thanks |
If I run build & serve or build:jit & serve, everything is working very well, but when I run start:dll or build:dll & start, I got the following information:
==================
�]0;webpack-dashboard��]0;webpack-dashboard��[?1049h�[?1h�=�[1;1r�[?25l�[1;1H�[H�[2J�[?1000h�[?1002h�[?1003h�[?1005h
Do you have any idea how do I fix it or how do I troubleshoot the issue ? Thank you!
The text was updated successfully, but these errors were encountered: