Enide Studio


News. Features. Demo. History. Usage. Download. Support. Support us. About. Donate. Gradle IDE Pack. Gradle for Eclipse - Android. AngularJS-Eclipse. Angular2-Eclipse. Polyglot Maven IDE Pack. .proto Editor. Nodeclipse CLI installer.

Version History & Roadmap


New major functionality is going to come from Eclipse, within standard Eclipse packages. Node.js goes mainstream.

That again shows rule that in the end tools are taken care by technology creators. As when competing with other stacks, such part as tooling does matter. (Compare with STS for Spring, and Red Hat JBoss tools for Hibernate etc.)

Eclipse Neon already has major Nodeclipse features and part:

  • JavaScript Editor with full EcmaScript 2015 (ES6) support. (Internally uses esprima, but not ternjs parser).
  • Chromium Debugger (moved to org.eclipse.wst.jsdt.chromium namespace) for Node.js debugging.
  • JSON editor for package.json, bower.json, .bowerrc, and .jshintrc. (Thanks for Angelo Zerr contribution)
  • npm, bower, Grunt & gulp support (again later 2 are of Angelo Zerr work)
  • markdown editing using WikiText Editor ( with some new bugs: e.g. got no letter appearing after pressing in WikiText Editor when editing markdown)

Not yet: Node perspective, wizards.

New: managing Node runtimes.

And of course would be awesome to see some thanks or just reference to Nodeclipse effort.

Version 1.1 (not released)

  • preference to add JSDT nature
  • disable JSDT nature by default over ES5 #70, Bug 442049 #159, ES6 #194
  • hot key for wizards (press letter after Alt+Shift+N)


  • by default enable JSDoc type checking

See tern-lint/wiki/Validation-JSDoc

Version 1.0.2 fix 2015-09-25 (released)

Version 1.0 2015-09-24 (released)

  • add Tern Explorer (alt Outline) view to the Node perspective atj#289
  • enable Tern Outline, ES6 by default in new Node.js project
  • pass environment variables to launched npm similar to Node debugging #177
  • #171 simple Bower support: Editor bower.json and .bowerrc, don’t validate or check for TODOs inside bower_components folder. Hint: add "postinstall" script into package.json :

    “scripts”: { … , “postinstall”: “bower install” },

  • #172 add template hello-angularjs in new Node.js project wizard
  • add Tern-Toolings wizards to Node perspective atj#204
  • #3 associate ._js files with Editors

Version .17.plus 2014-10-13

Version 0.17 Express 4.x and TernIDE support 2014-09-26

  • #154 hide “Node with Monitor” launcher - While more generic approach was tried (any monitor), this functionality was not finished, neither there were reposts on success or people willing to continue. However this feature was causing a lot of questions. Recommendation is to use TCF terminals to launch preferred monitor.
  • fix #158 Nodeclipse PreferenceInitializer was throwing Exception when could not find Node executable. That happened on Ubuntu where Node.js was installed with package manager. Note that you are advised get node name instead of nodejs as answered on Stackoverflow.
  • icons in Preferences pages
  • #160 #165 By default add Tern Nature, so that Tern completions will be enabled when Tern.java is installed. You will see doc when mouse over and completions options from node module of tern.
  • Tool Discovery at Developer Liberation Front is researching why developers are using and not using tools.
  • made with love, excellent Eclipse Zip (and Jar, Aar) Editor by Uwe Voigt mp. Listed in Help -> Nodeclipse Plugins List
  • #161 Express 4.x support (as discussed by @dwwaddell and @nodeleaf, also asked on SO):
    • associate Editor for www file (See SO)
    • stop raising exception when file is without Exception, but assume .js by default. So now you can launch www in Run and Debug mode. By the way, you can do without that but copying ./bin/www file into ./start.js in the project root (then you don’t need to look into bin folder):
console.log('starting Express server');
var debug = require('debug')('ProjectName');
var app = require('./app');

app.set('port', process.env.PORT || 3000);

var server = app.listen(app.get('port'), function() {
  debug('Express server listening on port ' + server.address().port);

Version 0.16 “ECT” 2014-06-09

Thanks to Pei-Tang Huang

All 4 are Listed in Help -> Nodeclipse Plugins List

Version 0.15.1 “Gradley” 2014-04-30

Thanks to @gurok, Chris and Teoh Han Hui

  • #39 [#49][49] color preferences for Gradle Editor, Chromium Debugger JS Editor and Minimalist Jade Editor
  • #137 Gradle, Maven - specify what JAVA_HOME to use. Hint: For gradle you also can use org.gradle.java.home property. See Chapter 20 The Build Environment.
  • #138 Gradle Deamon --deamon option enabled by default
  • #143 project config updated to enable JSDoc, TODOs processing (excluding node_modules). Note that for JavaScript validation JSHint-Eclipse is used, that is capable of EcmaScript 5 validation (configured in every project .jshintrc file "es5" : true)
  • #145 Gradle - option to use launch with wrapper
  • discovered Emmet (ex-Zen Coding) Eclipse plugin

Version 0.12 “Android friendly color” 2014-03-31

Thanks and hello to Ryan Knell for logo, John McCarthy, @Vexatos and Piotr Metel

  • close #7 Improving Code Assist - it was generic issue opened a year ago, no more new options came in the last 10 months
    • close #16 Improving Code Assist with JSDT and NJSDoc
    • close #27 Improving Code Assist with SublimeText-Nodejs
    • close #52 Improving Code Assist with VJET ANVIL (typelibs) - Eclipse VJET has not graduated from Eclipse incubator during 10 months.
    • close #54 Improving Code Assist with Marijnh Haverbeke’s Tern project, now it is tern.java project
    • close #117 Run Maven, Gradle or other batch-based script from Java (and then Eclipse) - actually done before in 0.11
  • #124 Preference option to “pass all environment variables of Eclipse to launched Node.js app” (for Node.js, Maven, Gradle). e.g. try

    task envvar « { System.getenv().each { key, value -> println “${key}/${value}” } }


  • fix #125 Gradle GUI for Android - “Could not create plugin of type ‘AppPlugin’; update Nodeclipse/Enide build.gradle template to 0.9.+
  • fix #127 “null” value for TMP (Thanks to @pchuong Patrick for raising issue)
  • #129 (experimental) Gradle Android - EnvVar to pass signingConfigs params
  • #130 Gradle Android - install to AVD
  • #131 Include Json Tools by Denis Mirochnik; disable JShint validation for .json files
  • add New TypeScript File wizard; add TypEcs TypeScript IDE for Eclipse by Axmor
  • #132 Include Ansi Console by Mihai Nita and Grep Console by Marian Schedenig. Try console.log("Hello \u001b[1;31mred\u001b[0m world!"); and check colors node package.
  • add updated Nodeclipse EditBox (created in 2009-2011 by Piotr Metel) - highlight code blocks using background colors themes.
  • #134 Minimalist Jade Editor idea is to define HTML tags and JavaScript keywords as words for highlight in Word.java and then use it together with EditBox
  • experimental content assist from Orion IndexFiles for amqp, express, mongodb, mysql, postgres and redis node packages.
  • make 3 type of content assist optional and enabled by default (change require restart as checking preferences each time assist is called would add delay)
  • add Nodeclipse CoffeeScript Editor 0.4.0 to Nodeclipse update site, be aware of #19 (“XtextReconcilerJob” has encountered a problem in 4.3.1 onwards)

Known issues: repository includes Eclipse plugin for LESS that can’t be installed.

Version 0.11 “Do It Yourself” 2014-02-25

Thanks to @nodeleaf Patrick Perroud for being the most active user and to @ihgreenman Ian Greenhoe for research on #81.

  • DIY: Make Eclipse yourself with Nodeclispe CLI Installer nodeclipse new from luna to d:/progs/eclipse-diy-luna/. Depending of your Internet connection speed, it may be long time, e.g. Operation completed in 942398 ms.
  • DIY: Code completions for other Node.js modules: Since Nodeclipse 0.9.0 there is code completion for base Node.js modules. What about others? Just create JSON file like:

    "module_completions": [
            "trigger": "MongoClient.connect(connectionString, function(err, db)",
            "name": "MongoClient.connect",
            "type": "method", // maybe also "event", "class" or "property"
            "desc": "MongoClient or how to connect in a new and better way http://mongodb.github.io/node-mongodb-native/driver-articles/mongoclient.html

The URL connection format

" } ] } </code></pre> Select it in Nodeclipse Preferences in "Alternative completion.json" path to give a try. (Only `trigger` is required for an entry) Got result that 'd like to share? Raise an issue and paste. Next version will have it shipped. - DIY: [How can you speed up Eclipse?](http://stackoverflow.com/questions/316265/how-can-you-speed-up-eclipse) - DIY: [External Tools](https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.help/contents/external-tools.md#external-tools) - ref [#23][23] DIY: [Is there an Eclipse plugin to run system shell in the Console?](http://stackoverflow.com/questions/1562600/is-there-an-eclipse-plugin-to-run-system-shell-in-the-console) - Windows ![](http://www.avajava.com/tutorials/eclipse/how-do-i-open-a-windows-command-prompt-in-my-console/how-do-i-open-a-windows-command-prompt-in-my-console-05.gif) - Linux, MacOS ![](http://alexruiz.developerblogs.com/files/2012/07/terminal21.png) - ref [#34][34] DIY: [JavaScript unit test tools for TDD](http://stackoverflow.com/questions/300855/javascript-unit-test-tools-for-tdd) From that list [Js-test-driver](http://code.google.com/p/js-test-driver/) is the one that has Eclipse plugin. There are also JUnit wrappers for JavaScript, not yet tried. - fix for [#81][81] "Node.js app with cluster does not execute inside Nodeclipse" (and [#92][92] "code with exec fails when running inside Eclipse on Windows" as it had the same remedy). Both were not technically bugs: `node` failed to execute because of missing environment variables, as @ihgreenman Ian Greenhoe has found out what "Unknown system errno 203" was. Now minimal set of env variables are passed automatically. [#122][122] is raised about Env variables Tab in Launch configuration. - [#120][120] Maven (Eclipse plugin) is updated to build Nodeclipse-1. Now you can launch project maven build without launching ugly Windows console. Instead of switching windows use Eclipse Workbench to show/hide View and build again. ![](/img/run-maven-build.png) [23]: https://github.com/Nodeclipse/nodeclipse-1/issues/23 [34]: https://github.com/Nodeclipse/nodeclipse-1/issues/34 [81]: https://github.com/Nodeclipse/nodeclipse-1/issues/81 [92]: https://github.com/Nodeclipse/nodeclipse-1/issues/92 [120]: https://github.com/Nodeclipse/nodeclipse-1/issues/120 [122]: https://github.com/Nodeclipse/nodeclipse-1/issues/122 ### Version 0.10.0 "ten" 2014-01-27 - code completion for base Node.js modules in JSDT-based Editor (read in 0.9.0 for TextEditor-based Editor ). For any issues check [#119][119] first. ![](/img/Completion-for-base-Node.js-modules.PNG) - update Launch icons (using great [Icons Editor](\enide\tools\eclipse-icons-editor) by Jabier Martinez) - fix filter for `npm` launch (Personally prefer Ctrl+Alt+D to launch shell.) - bundle with additional 5 plugins: - [YEdit (YAML)](/enide/tools/yedit) - [InstaSearch](/enide/tools/instasearch) - [Eclipse Color Theme](/enide/tools/eclipse-color-theme) (huge number of color themes for Editor; not recommended as some users report major issues) - [Chrome Theme](/enide/tools/eclipse-4-chrome-theme) (1 slide below; but actually has several themes, recommended) - [Moonrise UI Theme](/enide/tools/moonrise-ui-theme) (black; awesome, but yet not recommended as there is still issue [#49][49]) Moonrise Ubuntu Moonrise Ubuntu Moonrise Windows - [#100][100] [Enide repository](https://github.com/Enide/eclipse-p2-composite-repository) will contain ALL needed plugins. - [Enide Maven](https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.enide.maven) ([#117][117]) lets you launch maven build by right-clicking on `pom.xml`. - Nodeclipse CLI ([#91][91]) 0.10 now includes Maven and Gradle templates * Node.js run/debug function tested in Juno (ADT-BUndle), Kepler, Luna 4.4.M4 with JDK 7 on Windows 7. Raise an [issue](/#support) if you have or had issue on other version. [49]: https://github.com/Nodeclipse/nodeclipse-1/issues/49 [91]: https://github.com/Nodeclipse/nodeclipse-1/issues/91 [100]: https://github.com/Nodeclipse/nodeclipse-1/issues/100 [117]: https://github.com/Nodeclipse/nodeclipse-1/issues/117 [119]: https://github.com/Nodeclipse/nodeclipse-1/issues/119 ### Version 0.9.0 "completions 1/2", 2014-01-03 - [#97](https://github.com/Nodeclipse/nodeclipse-1/issues/97) set NODE_JUST_NODE on Windows only; so that new users on other OSes, check preferences first. - in Node.js project Wizard select what template to use. (The same list as for [Nodeclipse CLI](https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.ui/templates) `npm i -g nodeclipse` ) - new hello-html, hello-coffee, hello-typescript templates - workspace-wide NODE_OPTIONS (set in Preferences). This lets you run node(1) with the `--harmony` flag that is needed to enable __generators__ support (since __node 0.11.9__). And yes, you still can set Node arguments in __Node.js Application__ Run/Debug LaunchConfiguration per every file you launch. - workspace-wide NODE_APPLICATION_ARGUMENTS (set in Preferences). Similarly, arguments from Preferences and from arguments from LaunchConfiguration are all applied. - ref [#95](https://github.com/Nodeclipse/nodeclipse-1/issues/95) (when Node.js sources directory is selected in Preferences) automatically link to Node.js sources `lib` directory. It is actually quick & lazy implementation just by adding LinkedFolder into `.project` like node_lib 2 D:/Nodejs/sources/node-v0.10.22/lib </link> (`.settings/com.eclipsesource.jshint.ui.prefs` file was updated to exclude `node_lib` from JSHint processing). Note that linked JavaScript is not read-only, so if you references git clone of Node.js sources, you are ready to develop Node.js runtime) - as work in progress (for Nodeclipse Node.js Editor associated by default with `*.njs` files) code completion for base Node.js modules shows [APIs](http://www.nodejs.org/api/) ([sources](https://github.com/joyent/node/tree/master/doc/api)). - and [completion proposals](https://github.com/Enide/nodeclipse-1/blob/master/org.nodeclipse.ui/src/org/nodeclipse/ui/contentassist/completions.json). Point in Preferences to local `completion.json` to define your own, or to empty file like snippet below to disable it: { "completions": [ { "trigger": "ArrayBuffer();" }, { "trigger": "Int8Array();" } ] } - there sprint goal was to make Node specific content assist in Node JSDT-based Editor, however I [Paul Verest] ran into problem that can't be solved quickly: [Content assist with javaCompletionProposalComputer for Eclipse JSDT gives no proposal](http://stackoverflow.com/questions/20779899/content-assist-with-javacompletionproposalcomputer-for-eclipse-jsdt-gives-no-pro) ### Version 0.8 "wizards", 2013-12-02 - jshtml and hogan.js template engines in [Express Wizard](https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.ui/src/org/nodeclipse/ui/wizards/ExpressProjectWizardPage.java#L215-L225) - Stylesheet engines selection in Express Wizard (however correctly generated command line execution gives css only on Windows) - PhantomJS wizard - Nashorn wizard - less strict [JSHint defaults][14] - update [GFMV][3] to 1.7 - add less known Other Optional Tools: - [Glance by Xored](http://ystrot.github.io/glance/) (Highlight anywhere, Ctrl+Alt+F; lets you search almost every place in Eclipse you can imagine) - [PracticallyMacro by Ernest Pasour](http://sourceforge.net/projects/practicalmacro/) (Macros for Editors using [BeanShell.org](http://www.beanshell.org/)) - [EclipseRunner by Lukasz Wachowicz and Bartosz Roznowski (Runner View)](http://code.google.com/p/eclipserunnerplugin/) - [SelectionExplorer (PDE) by Sandip Chitales](http://code.google.com/p/sandipchitaleseclipseplugins/#Selection_Explorer) Known issues: markdown.editor.feature is missing inside 0.8.0 update repository. Check for Markdown Editor inside [Nodeclipse Plugins List](http://www.nodeclipse.org/updates/list) or use update site
### Version 0.7 "run it!", 2013-11-01 - allow many Node.js application running, add Debug View in Node perspective to check and terminate processes - optional support for [PhantomJS][8] (run) - optional support for [Nashorn JJS][9] (run) - optional support for [MongoDB][13] Shell (running scripts) - disable JSDT validation; enable JSHint validation for `*.json, *.njs, *.pjs, *.jjs, *.mjs, *.jshintrc` files - add the most strict [`.jshintrc` template][14] - Help content with tutorials, links and examples, that you can [edit online with GitHub][10] - Update [Github Flavored Markdown Viewer][3] by Satyagraha, [StartExplorer][4] by Bastian Krol, Nodeclipse [Git Addon][6] by Paul Verest, [JSHint][15] integration for Eclipse, [developed by Ralf Stenberg at EclipseSource][16] - Add [Icons Editor](http://code.google.com/a/eclipselabs.org/p/eclipse-icons-editor/) 2.4.0 as `*.png` Editor by Jabier Martinez (requires org.eclipse.draw2d), PDE-Tools [mp](http://marketplace.eclipse.org/content/pde-tools),[sources](https://github.com/jeeeyul/pde-tools) by Jeeeyul, Regular Expression [Eclipse Regexp](http://marketplace.eclipse.org/content/eclipse-regexp) [github](https://github.com/zapletnev/eclipse-regexp) by Igor Zapletnev, MonjaDB (MongoDB GUI) by Kanatoko Anvil [sources](https://github.com/Kanatoko/MonjaDB), [mp](http://marketplace.eclipse.org/content/monjadb) - Known issues: [gfm_viewer#39](https://github.com/satyagraha/gfm_viewer/issues/39) NPE while debugging (GFM View in Node, not Debug perspective). Just close GFM View when about to debug. (Recommended is keep an eye on errors in Error Log View). [8]: http://phantomjs.org/ [9]: https://blogs.oracle.com/nashorn/ [13]: http://www.mongodb.org/ [14]: https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.ui/templates/common-templates/.jshintrc ### Version 0.6, 2013-10-06 - Option to launch Node debug without -brk (disable interruption of Node.js app on the first line). Check Help (F1) Debug page on -debug-brk option. - [#61](https://github.com/Nodeclipse/nodeclipse-1/issues/61) set debugging port in Preferences. Now you can debug several Node.js apps in the same time (but in different Eclipse instances). - [Extended Help with examples and links][10]. Ready for contribution: just edit online with GitHub. - Chromium JS Editor now has Outline support as Node Editor - TODO: 2 items below have run into problem <http://stackoverflow.com/questions/19157302/eclipse-plugin-development-saved-launchconfiguration-overrides-launchtype> , that limits their usability (also warning in Help). Decision was made not to postpone release of features above and have more frequent releases - more support for [CoffeeScript][1] (launch `coffee` util in RUN or DEBUG mode) & [TypeScript][2] (`tsc` compiler). Note that full featured CoffeeScript debugging [#12][12] is not yet implemented. Do you know Java library for parsing `coffee`-generated SourceMaps? [#12][12] - [#57](https://github.com/Nodeclipse/nodeclipse-1/issues/57) running app.js with node-dev, forever, supervisor, nodemon etc. Default preferences to `node-dev`. - Integrate [Github Flavored Markdown Viewer][3] by Satyagraha, [RestClient Tool](/restclient-tool) by Yadu Vendra, [StartExplorer][4] by Bastian Krol, Nodeclipse [Git Addon][6] & [Plugins List][7] by Paul Verest [1]: http://coffeescript.org/ [2]: http://www.typescriptlang.org/ [3]: https://github.com/satyagraha/gfm_viewer [4]: http://basti1302.github.io/startexplorer/ [6]: http://www.nodeclipse.org/git/addon/ [7]: https://marketplace.eclipse.org/content/nodeclipse-plugins-list [10]: https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.help/contents#intro [12]: https://github.com/Nodeclipse/nodeclipse-1/issues/12 ### Version 0.5, 2013-09-08 - [#59](https://github.com/Nodeclipse/nodeclipse-1/issues/59) setting environment variables in Launch (Run/Debug Configuration) - [#26](https://github.com/Nodeclipse/nodeclipse-1/issues/26) [CoffeeScript support](http://coffeescript.org): run `*.coffee` files - [#17](https://github.com/Nodeclipse/nodeclipse-1/issues/17) bundle [Express](http://expressjs.org/) and CoffeeScript into jar files. This lets you install them even if you don't have admin permission on computer that you use, or if you want play quickly with Node.js and don't remember how to do `npm install express -g`. Note this bundle is of current Express/CoffeeScript versions, and doesn't check for your Node.js version compatibility (the latest version is assumed). - [#66](https://github.com/Nodeclipse/nodeclipse-1/issues/66) built-in (Help -> Help Contents) and [online help](https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.help/contents). It is open-sourced and written in Markdown. [Welcome to contribute](https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.help/contents): just edit Markdown files online, then send pull request. - [#40](https://github.com/Nodeclipse/nodeclipse-1/issues/40) [maven](http://maven.apache.org/) build. Building Nodeclipse is now the easiest `mvn package` from command line. [Check README](https://github.com/Nodeclipse/nodeclipse-1#maven-build) ### Version 0.4, 2013-05-19 ### Version ver 0.3, 2013-04 - Add support for [JSHint][15] integration for Eclipse, [developed by Ralf Stenberg at EclipseSource][16] You had to set project property for JSHint for each project creating. It was boring task.
Nodeclipse 0.3 will set them automatically when generating Node project and Express project.
You should install JSHint integration for Eclipse.
Update site: http://github.eclipsesource.com/jshint-eclipse/updates/ - Update template for new project * Add README.md template * Add hello-world-server.js * Add package.json [(This is good practice)](http://blog.nodejitsu.com/package-dependencies-done-right) * [Publish](http://marketplace.eclipse.org/quickstart) on Eclipse marketplace * [t#3 [Feature Request] allow passing arguments](https://github.com/tomotaro1065/nodeclipse/issues/3) You can pass arguments to application and node.js setting on [Debug configuration...]-[Node Application]-[&ltyour configuration name&gt]-[Arguments].
You can also set arguments on [Run configuration...].
![Screen shot](/img/Arguments.png) * [n#2 on x64 windows doesn't find NodeJS dir automatically](https://github.com/Nodeclipse/nodeclipse/issues/2) * [#5 When creating Node project and folder already exists, then add only .project file and don't add 3 files (README.md, hello-world-server.js, package.json)](https://github.com/Nodeclipse/nodeclipse-1/issues/5) * [#6 Add Express Project in main menu under File -> New (in Node perspective)](https://github.com/Nodeclipse/nodeclipse-1/issues/6)
If [Node Express Project] menu does not appear under File->New, reset [Node] perspective by right-clicking on the [Node] button, which is located perspective switching area.
![ResetPerspective](/img/ResetPerspective.png) [15]: http://www.jshint.com/ [16]: https://github.com/eclipsesource/jshint-eclipse ### Version ver 0.2 by Tomoyuki Inagaki - Integrating Chromium Development Tools & Debugger ([historical link](http://stackoverflow.com/questions/8159238/eclpse-and-node-js-debug)). ### Version ver 0.1 - Node perspective - Run as Node application - Console integration - npm operations - ...
comments powered by Disqus