Bugzilla – Full Text Bug Listing
| Summary: | Add 'npm init' support to the shell | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Lee Surprenant <lmsurpre> |
| Component: | Node | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |
Havn't tried it on Orion proper, but on OrionNode 'npm init' presents me with the interactive npm init dialog and an 'in progress' bar showing me a process is running. Unfortunately, I don't see a way to provide the input to this interactive prompt and there is nothing I can do to kill that process. I guess supporting this would require support for input to a process on the shell? If that is difficult, could we at least prevent the user from trying it? For instance, documentation could be updated to include the support subcommands. Currently 'help npm' presents you with the following Description: Runs the node package manager. Parameters: args (array, optional) The command-line arguments to pass to npm. output (file, optional) The file or directory to re-direct output to No guidance is given about which npm args are allowed and which are not.