Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable "Set as Node.js Startup File" context menu item for all filetypes #65

Closed
mousetraps opened this issue Apr 13, 2015 · 0 comments · Fixed by #153
Closed

Enable "Set as Node.js Startup File" context menu item for all filetypes #65

mousetraps opened this issue Apr 13, 2015 · 0 comments · Fixed by #153

Comments

@mousetraps
Copy link
Contributor

Right now you can only set js and ts files as startup. This becomes an issue with things like express where .\bin\www should be the startup file (see #27)

@mousetraps mousetraps added the bug label Apr 13, 2015
@mousetraps mousetraps changed the title Enable "Set as Node.js Startup File" context menu item for all files Enable "Set as Node.js Startup File" context menu item for all filetypes Apr 13, 2015
@mousetraps mousetraps self-assigned this May 5, 2015
@mousetraps mousetraps modified the milestones: June, May May 5, 2015
mousetraps added a commit to mousetraps/nodejstools that referenced this issue Jun 1, 2015
Fix microsoft#86 startup file setting breaks debugger
- rename "Node.exe arguments" -> "Node.exe options" to be consistent with
  node --help
- rearrange arguments so that they are in the order they are supposed to
  be appended to one another
- create a new "script (startup file)" property so that it is visible
  what arguments are getting passed to node from the General properties
  page, and doesn't block right clicking the file and setting as startup
  file or modifying it from file properties.

Fix microsoft#65 Enable "Set as Node.js Startup File" context menu item for all
filetypes
- add a special case for when there is no exension specified, as is the
  case in the default express 4 template.
mousetraps added a commit to mousetraps/nodejstools that referenced this issue Jun 1, 2015
Fix microsoft#66 startup file setting breaks debugger
- rename "Node.exe arguments" -> "Node.exe options" to be consistent with
  node --help
- rearrange arguments so that they are in the order they are supposed to
  be appended to one another
- create a new "script (startup file)" property so that it is visible
  what arguments are getting passed to node from the General properties
  page, and doesn't block right clicking the file and setting as startup
  file or modifying it from file properties.

Fix microsoft#65 Enable "Set as Node.js Startup File" context menu item for all
filetypes
- add a special case for when there is no exension specified, as is the
  case in the default express 4 template.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant