Comments (11)
I just tested debugging my own production app with WebStorm 11.0.3 and node.js 5.10.0 and am experiencing some issues as well. However, since I am usually using node v4 it may be something different from your issue. In my case node server.js
works fine as well. When I use the debugger the boot process doesn't finish. However, fireUp# INFO Validating all inject references done.
was already printed and all the modules get loaded / injected to a certain extend - at least the console output of fire-up's activity is complete.
Could you give me more details like some sample code and your exact versions so that I can reproduce your issue?
from fire-up.
Wow. Great customer service :-)
I have exactly the same symptoms as you, except in my case I can get it to work with 5.0.0, but no later.
Im using vs-code 0.91/webstorm 2016.1. The code is a bit complicated, since i created a small App class to make things simpler, but based on your description it seems were hitting the same issue.
from fire-up.
:D You are welcome.
I just realized that the boot process is actually working but really slow. 100x slower or so. Could you apply some patience ;) and see if that is the case for you, too?
from fire-up.
In webstorm debug startup is slow regardless, which is why i use vs-code to debug (its very fast). But in this case I left vs-code alone for over 10 minutes with no joy.
from fire-up.
Does the boot process finish after some time when using the WebStorm debugger?
Could you pause the debugger is vs-code to see where the app is waiting?
from fire-up.
No, it hangs the same in both Webstorm and VsCode. Give me a second - let me fiddle with the debugger a bit.
from fire-up.
Spent a couple minutes getting into this, but for now it seems like a Heisenburg. Stepping through causes it to stop at an even earlier point.
from fire-up.
Haha.
I got a little more insight for what at least I see in my system:
- I updated all of fire-up's dependencies. Did not make a difference. Anyhow, I will publish a newer version of fire-up later today.
- The slow startup is related to
require(...)
calls. I can say that it is not related to fire-up. Rather something related to node and the debugger.
If you want to test if your code is hanging at some require(...)
call please go to node_modules/fire-up/lib/std/require.js
and replace:
if (_.isFunction(options.require)) {
return options.require(id);
} else {
try {
return require.main.require(id);
} catch (e) {
if (id.charAt(0) !== '/') {
fireUp.log.debug({}, "The dependency injection wrapper for require uses the main require function which may not always use the search paths you intended.");
fireUp.log.debug({}, "You may pass your own require function like this: fireUpLib.newInjector({ ..., require: require });");
}
throw e;
}
}
with:
if (_.isFunction(options.require)) {
console.log(' ---> require('+id+')');
var temp = options.require(id);
console.log(' <--- require('+id+')');
return temp;
//return options.require(id);
} else {
try {
console.log(' ---> require.main.require('+id+')');
var temp = options.require(id);
console.log(' <--- require.main.require('+id+')');
return temp;
//return require.main.require(id);
} catch (e) {
if (id.charAt(0) !== '/') {
fireUp.log.debug({}, "The dependency injection wrapper for require uses the main require function which may not always use the search paths you intended.");
fireUp.log.debug({}, "You may pass your own require function like this: fireUpLib.newInjector({ ..., require: require });");
}
throw e;
}
}
If it prints out --->
and keeps you waiting for the <---
you have the same issue as I do. Let me know what you find out!
from fire-up.
Btw, see develar's comment at the end of nodejs/node-v0.x-archive#9125 Seems like their fix will solve this issue as well.
from fire-up.
FWIW, I just released [email protected]
. You may try debugging with this version.
from fire-up.
Thanks a million. I'll give it a shot.
from fire-up.
Related Issues (2)
- Basic questions HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fire-up.