| layout | title |
|---|---|
home |
Nodeclipse -- Version History |
Suggest new and vote for ideas for Nodeclipse or raise an issue.
10 ways to support free software you love, 9 won’t cost you a dime
Reminder: reset perspective after an update for new UI elements to appear.
-
jshtml and hogan.js template engines in Express Wizard
-
Styleshhet engines selection in Express Wizard (however correctly generated command line executon gives css only on Windows)
-
PhantomJS wizard
-
Nashorn wizard
-
less strict JSHint defaults
-
update GFMV to 1.7
-
add less known Other Optional Tools:
- Glance by Xored (Highlight anywhere, Ctrl+Alt+F; lets you search almost every place in Eclipse you can imagine)
- PracticallyMacro by Ernest Pasour (Macros for Editors using BeanShell.org)
- EclipseRunner by Lukasz Wachowicz and Bartosz Roznowski (Runner View)
- SelectionExplorer (PDE) by Sandip Chitales
-
Known issues: markdown.editor.feature is missing inside 0.8.0 update repository. Check for Markdown Editor inside Nodeclipse Plugins List or use update site
http://dl.bintray.com/enide/Markdown/1.0.0/
- allow many Node.js application running, add Debug View in Node perspective to check and terminate processes
- optional support for PhantomJS (run)
- optional support for Nashorn JJS (run)
- optional support for MongoDB Shell (running scripts)
- disable JSDT validation; enable JSHint validation for
*.json, *.njs, *.pjs, *.jjs, *.mjs, *.jshintrcfiles - add the most strict
.jshintrctemplate - Help content with tutorials, links and examples, that you can edit online with GitHub
- Update Github Flavored Markdown Viewer by Satyagraha, StartExplorer by Bastian Krol,
Nodeclipse Git Addon by Paul Verest,
JSHint integration for Eclipse, developed by Ralf Stenberg at EclipseSource - Add Icons Editor 2.4.0 as
*.pngEditor by Jabier Martinez (requires org.eclipse.draw2d), PDE-Tools mp,sources by Jeeeyul, Regular Expression Eclipse Regexp github by Igor Zapletnev, MonjaDB (MongoDB GUI) by Kanatoko Anvil sources, mp - Known issues: gfm_viewer#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).
- 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 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. 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 (launch
coffeeutil in RUN or DEBUG mode) & TypeScript (tsccompiler). Note that full featured CoffeeScript debugging #12 is not yet implemented. Do you know Java library for parsingcoffee-generated SourceMaps? #12 - #57 running app.js with node-dev, forever, supervisor, nodemon etc.
Default preferences to
node-dev.
- more support for CoffeeScript (launch
- Integrate Github Flavored Markdown Viewer by Satyagraha, RestClient Tool by Yadu Vendra, StartExplorer by Bastian Krol, Nodeclipse Git Addon & Plugins List by Paul Verest
- #59 setting environment variables in Launch (Run/Debug Configuration)
- #26 CoffeeScript support: run
*.coffeefiles
- #17 bundle Express 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 built-in (Help -> Help Contents) and online help. It is open-sourced and written in Markdown. Welcome to contribute: just edit Markdown files online, then send pull request.
- #40 maven build.
Building Nodeclipse is now the easiest
mvn packagefrom command line. Check README
- Integration with JSDT (Code Assist and Outline)
#11 [Feature request] Outlines and other things for class-y structure?
- Integration with Markdown viewer
29 Integrate Markdown Editor, add Markdown HTML preview to Node perspective
- #37 Enhancement: Ability to set a working directory
- #36 Associate *.json files with JS Editor
- #25 Node perspective doesn't support working sets
- Add support for JSHint integration for Eclipse, developed by Ralf Stenberg at EclipseSource
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)
- Publish on Eclipse marketplace
- t#3 [Feature Request] allow passing arguments
You can pass arguments to application and node.js setting on [Debug configration...]-[Node Application]-[<your configration name>]-[Arguments].
You can also set arguments on [Run configuration...].
- n#2 on x64 windows doesn't find NodeJS dir automatically
- #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)
- #6 Add Express Project in main menu under File -> New (in Node perspective)
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.
by Tomoyuki Inagaki
- Integrating Chromium Development Tools & Debugger (historical link).
- Node perspective
- Run as Node application
- Console integration
- npm operations
- ...