Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New TS projects require npm on the PATH

Open
#2,179 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js, typescript
Domain
build-system, devtools

Research direction

Reproduce the blank TypeScript Node.js console application build with node and npm absent from PATH. Inspect Microsoft.NodejsToolsV2.targets at line 60 and compare the generated .njsproj behavior with the older project linked in the report. Done means a newly created project either builds without requiring PATH entries or reports an unsupported configuration.

Written by the indexing model from the issue text.

Description

I have 2 projects, one created with VS 2019 and another with VS2019.1. The latter doesn't build because I don't have npm in the PATH.

Expected Behavior

When you create a project it just works or reports an unsupported configuration

Actual Behavior

When you create a project in VS 2019.1 it reports a build error out of the box. That is, empty typescript node.js console application doesn't build after the wizard.

  • NTVS Version: 1.5.10424.1
  • Visual Studio Version: 16.1.2
  • Node.js Version: 10.15.3
Steps to Reproduce
  1. Ensure that neither npm nor nodejs are on your PATH
  2. Open VS 2019.1
  3. Create new project
  4. Filter by Language:Typescript
  5. Blank node.js console application
  6. Next
  7. Create
  8. Solution opens
  9. Press F6 to build
  10. It reports error MSB3073:
------ Build started: Project: NodejsConsoleApp2, Configuration: Debug Any CPU ------
		'npm' is not recognized as an internal or external command,
		operable program or batch file.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\Node.js Tools\Microsoft.NodejsToolsV2.targets(60,5): error MSB3073: The command "npm run build" exited with code 9009.
Done building project "NodejsConsoleApp2.njsproj" -- FAILED.

Build FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========

At the same time an older project https://pastebin.com/MFEyHKyk works without requiring either npm or node to be in PATH.

Dominant language
C#
Stars
1.8k
Forks
355
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/nodejstools

All issues in microsoft/nodejstools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.