Node.js Code Assist in the Eclipse Debugger - eclipse

Does anyone know how to get code-assist working while debugging (say for instance while forming a watch expression) Node.js in Eclipse?
One of the motivations for my wanting to use Node.js on the server side was the idea that I could debug applications just as easily as I can debug client-side javascript code in a browser console like the one Chrome includes.
This seems like it should be a pretty easy one.
Thanks in advance.

For better Node.js debugging in Eclipse there is Nodeclipse project http://www.nodeclipse.org/updates/
It comes with Tern that gives mouse over hints

Related

How can i open another terminal in Whack Whack terminal?

I'm trying to support two web applications on the same IDE (Visual Studio ) but not sure how can i have two terminals open. I would appreciate your help thank you!
Alright just so that if anyone comes across this block, they can get to know my experience.
I'm building a chat application using React and Socket.io and I'm using Visual Studio (IDE different than Visual Studio Code (text editor)). In order to run the react application and the server together I needed two terminals open at the same time to invoke functions(send messages) within the application and listen on the server for a response.
How I was able to do it
I already had the Whack Whack Terminal Extension downloaded and running and then i used the Developer Command Prompt where you can access in Tools/Command Line/Developer Command Prompt.
I hope this might come helpful to anyone who comes across this!

Start Point for writing own debugger extension for Visual Studio Code

I want to migrate from Eclipse based IDE to VSC for working with remote Ruby apps and I stuck with writing VSC debugger extension.
Currently, the debugger in the Ruby App and debugger part in Eclipse IDE communicates via HTTP.
I have read the known widely article "Debugger Extension" and don't have yet clear understanding how exact to do it.
In my mind I must use Server type of VSC debugger, which starts to listen HTTP on specific port and translate commands to from DAP. But I cannot get workable sample of this.
Do somebody smthng like this?

Any disadvantage using Terminal as opposed to the deprecated GoogleAppEngineLauncher?

I'm doing Udacity's Web Development course. I've heard some users talk about Eclipse, but I'd rather have a basic understanding of the command line than move on to that higher level software.
Is there anything on a Mac that I can't do in Terminal that I could on Google App Engine Launcher?
Thank you.
The gcloud commands from the Cloud SDK provide much more control over your experience. The App Engine Launcher actually causes more problems than it helps with. In the long run, you're much better off with gcloud.
If you wanted to use an IDE, there are new plugins for Eclipse and IntelliJ. If you wanted to keep debugging simple, you could just use the command-line PDB debugger.

Features and Configuration of the Typescript Eclipse Plugin

I'm interested in developing with typescript on linux. So I found the above mentioned plugin. I installed eclipse and also the eclipse-typescript plugin as described here. Now I can edit typescript files and see the highlighting. But it is not possible to debug a script. When I try to debug it, there is no debug configuration available.
Is the plugin able to debug a typescript?
I also read in this wiki, but this single page doesn't help me. I googled around and did not found any howto or help...
Thanks
Is the plugin able to debug a typescript?
It isn't supported. Based on my empirical (but certain) observation of : https://github.com/palantir/eclipse-typescript/tree/master/Bridge/src
You could debug the generated JavaScript though (and I highly recommend you do that anyways). And in fact learn to use google chrome debug tools (you'll thank me someday) since they have a live edit and continue, repl, profiler etc.
Alternatively you can try WebStorm which fully supports debugging TypeScript on linux.
At the same time, TypEcs (another TypeScript plugin for Eclipse) features debugging - http://typecsdev.com/. The plugin supports two modes of TypeScript debug:
Standalone: this mode is suitable for debugging server-side NodeJS applications written on TypeScript,
Web Remote: this mode is connected to Google Chrome web browser and allows you to debug TypeScript web application.
So you can try this one.

PyDev Breakpoints in App Engine 1.7.6 broken?

I just upgraded to the App Engine 1.7.6 SDK for my python app and realised that breakpoints no longer work in PyDev (Eclipse plugin) when using the new dev_appserver.py.
Does anyone know of a way of enabling them again? I assume the new server is spawning a new process for the web server, and the debugger isn't attaching to that one. I'm not sure how to configure it to do that though.
In the meantime I am using the old_dev_appserver.py server.
UPDATE 2012-07-27:
Following the comment, I verified, the issue is solved after updating to
PyDev. 2.8 and App Engine 1.8.2
OBSOLETE:
I found the following analysis of the problem at googleappengine issues tracker
The reason why PDB doesn't work is because dev_appserver is using
stdin/stdout for interprocess communication. Python has built-in
libraries for IPC: http://docs.python.org/2/library/ipc.html.
dev_appserver should use these, and then stdin/stdout can be left
alone so that PDB still works.
So it seems that there is no workaround, rather than reverting to use old_dev_appserver.py
UPDATE 2013-04-23:
Inability to debug is annoying.
Many developers complain about it
PyDev Breakpoints in App Engine 1.7.6 broken?
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/ep5BWYKpQpU
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/TCQuJpF44cY
https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28
https://code.google.com/p/googleappengine/issues/detail?id=9012
I am keeping track of the development of this issue here:
http://goo.gl/XRU01
Yep, ran into the same problem.
Open your Run/Debug Configuration and set the Main Module to:
${GOOGLE_APP_ENGINE}/old_dev_appserver.py
Do you mean pdb.set_trace() isn't working?
Look for the function MonkeyPatchPdb() in google/appengine/tools/dev_appserver.py
Run that somewehere in your own project before you use pdb and it should fix it.