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
debug('Listening on ' + bind) doesn't output anything #72
Comments
Hi! So the output from the generator itself should have said your environment variable needs to be |
I'm also assuming your app is actually called "myapp". The generator's own output will tell you the true environment variable to set. From your link, it should have told you |
So, in my package.json: {
"name": "myapp",
"main": "app.js",
"scripts": {
"start": "node ./bin/www",
"debug": "DEBUG=myapp node ./bin/www"
}, In the shell: DEBUG=myapp:* In var debug = require('debug')('myapp:server'); |
Ok... We don't add a |
What is the output of |
Yeah the debug was mine. No one uses it anyway. Will delete.
|
But otherwise, it should print out following the debug command the generatory tool should have displayed to you:
(note that |
Yeah, I just don't see this output anything to the shell:
|
I'm not having that issue here. Can you send me the complete application you are trying to use (upload to like a Github repo)? Creating a new application here works perfectly:
I don't know what else to say. |
Weird. It just started working on myapp. Rubber-duck debugging at its finest. Tried this one, and fine as well. https://github.com/kevinSuttle/express-generator-socket Thanks anyway, @dougwilson. Wish I could point to something that changed so that future people that stumble upon this could have something useful. :/ |
Hm, that's really weird. I really hate that too :( Typically I usually lock complete issues on GitHub, but I'm leaving this open in case you find out what it was and want to post here :) |
Fix example
In reference to the line in the generated
bin/www
I never seem to get any output to my shell from this, even setting:
Am I totally doing this wrong?
The text was updated successfully, but these errors were encountered: