Package Exports
- nodeclipse
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (nodeclipse) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Nodeclipse CLI
Node.js Development with Eclipse or Enide Studio
Install with npm install -g nodeclipse
Usage: just run nodeclipse -p to add needed .project file to current directory
In Eclipse File -> Import -> General / Existing Projects into Workspace
Check http://www.nodeclipse.org/ on how to get Nodeclipse or Enide Studio
Commands
Usage: nodeclipse [arguments]
Arguments:
-c, --create <name> create project folder <name> [using template] and prepare it
-u, --use <template> use/copy specified template when creating project
-p, --prepare prepare Nodeclipse [Node.js] project for import, i.e. add needed `.project`
and other `.*` files ('.gitignore', '.jshintrc', '.settings/') if there is no `.project` yet
-g, --eclipse_project_general prepare General Eclipse project for import, i.e. add only needed `.project` file
-n, --name [<name>] project name (default is folder name)
-h, --help Check README
-v, --version print nodeclipse CLI's version
-V, --verbose be verbose
Templates are just folders in this project sources:
hello-world The famous hello world HTTP server in 6 lines
hello-coffee The same server written in CoffeeScript
hello-typescript The same server written in TypeScript
hello-html Template with HTML fileExamples:
nodeclipse -p
nodeclipse --prepare project1
nodeclipse --create project2
nodeclipse --create project3 --use hello-coffee
nodeclipse -c project4 -u hello-coffeeEclipse Workspace and Project
Eclipse Workspace is just folder that contains Eclipse Projects.
Eclipse Projects is just folder with .project file.
Developing Nodeclipse CLI
Project sources are at https://github.com/Nodeclipse/nodeclipse-1 under https://github.com/Nodeclipse/nodeclipse-1/tree/master/org.nodeclipse.ui/templates
https://npmjs.org/doc/developers.html
before publishing
- try with
npm install . -g - check that nodeclipse.js line ending is UNIX style (#101)
#4341 common-templates/.gitignore becomes common-templates/.npmignore
Links
The only feature that differentiates a command-line program from a library is the bin field in the package.json file.
http://howtonode.org/how-to-module
Ideas
$ nodeclipse -h
Usage: nodeclipse [directory] [arguments]
-f, --force force on non-empty directory (by default existing files are not updated)
-pg as general project
-pn as Nodeclipse Node.js project (default)
-t, --template <template> use/copy specified template when creating project (see also `git init`)
--gitclone <repository> call git clone [directory]
--js2njs (renamejs)
--njs2js
TODO Examples:
git clone repository directory
nodeclipse directory -pg
nodeclipse directory -pg --gitclone repository
nodeclipse --gitclone repository directory -pg (bad?)Dream - I wish I could get current project in GitHub as project in Eclipse with 1 click. options are:
eclipse wizards accessible with icon, where I only need to git repository URL
add link on Wizard Page
options to refine .jshintrc
History
0.8.2 fix #101 (bug on MacOS); -g option 0.8.3 fix general project template