Skip to content

error running debugger and some other oddities #136

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

Closed
oivinds opened this issue Mar 19, 2014 · 2 comments
Closed

error running debugger and some other oddities #136

oivinds opened this issue Mar 19, 2014 · 2 comments

Comments

@oivinds
Copy link

oivinds commented Mar 19, 2014

This is errors I get trying twice to install and run this setup. Since nobody else apparently has had these errors I of course think It could be my fault. Yet, the dependencies
are defined by this generator. My node version is v0.10.24

ISSUE 1.
I followed the instructions and selected all options for install and ran "sudo grunt serve:debug"

Terminal log:
"[nodemon] v1.0.15
[nodemon] to restart at any time, enter rs
[nodemon] watching: .
[nodemon] starting node --debug-brk server.js
debugger listening on port 5858
Node Inspector v0.7.1
Visit http://localhost:8080/debug?port=5858 to start debugging."

Terminal opens Safari browser:
-http://localhost:8080/debug?port=5858
Where I get this console error message:

"[Error] SyntaxError: Unexpected token ',' (ConsoleMessage.js, line 231)
[Error] TypeError: 'undefined' is not an object (evaluating 'WebInspector.ConsoleMessageImpl.prototype')
global code (ConsoleView.js, line 1163)
[Error] TypeError: 'undefined' is not a constructor (evaluating 'new WebInspector.ConsoleGroup(null)')
ConsoleView (ConsoleView.js, line 72)
_doLoadedDoneWithCapabilities (inspector.js, line 473)
(anonym funksjon)
_initializeCapability (inspector.js, line 301)
(anonym funksjon)
dispatch (InspectorBackend.js, line 220)
onWebSocketMessage (Overrides.js, line 44)"

If however i paste the url : http://localhost:8080/debug?port=5858 in to Chrome I do not get the error message above. Instead I get 2 labels on top left of the browser window named "sources" and "console" that do not output anything when browsing?

ISSUE 2

trying to run "sudo grunt serve:dist "
Here I believe imagemin is flaky, It generates a empty file of the minified version of yeoman.png.
Also, the content of generated file "vendor.css" is not what one would expect, see image
skjermbilde 2014-03-19 kl 16 15 12
I had to use sudo to make "grunt serve:dist" delete and write folders.

So beeing a relative noob when it comes to Grunt and related automation tasks, Should I just clear away from this otherwise smart tool? If I triy to fix something in this generator, I fear something else would break. Any sound advise?

@DaftMonk
Copy link
Member

The imagemin error is a problem with their new version. The workaround is to disable caching as shown here #123.

The path to your vendor.css is being included even though it doesn't exist, which happens if you don't have any vendor css files in your app. Just fyi, when a file doesn't exist it will look like an index.html file. This is because the routes are setup to always render the index.html file by default (this is necessary for html5 location mode to work when you try to go directly to a url in your angular app.)

I don't think it should cause any problems, but I will look into a way to remove the vendor.css link rel when there's no source file.

The node inspector error is because Safari is not supported. From their github readme:

NOTE: Node Inspector works in Chrome and Opera only. You have to re-open the inspector page in one of those browsers if another browser is your default web browser (e.g. Safari or Internet Explorer).

It should work in chrome though, just make sure you closed out the safari debugger tab before loading it in chrome.

@oivinds
Copy link
Author

oivinds commented Mar 20, 2014

Extremely grateful for your feedback. I'll have a go at it :-)

@oivinds oivinds closed this as completed Mar 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants