Node.js tools are unavailable on my project.

Open
#2,258 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, node.js
Domain
developer-experience, tooling

Research direction

Start by reproducing the missing Restore Packages action and node_modules icon in Visual Studio 2019 for a netcoreapp2.2 Class Library containing package.json. Trace how Node.js Tools detects project types and determine whether this project type is supported; done means the compatibility behavior and any required setup are clearly established.

Written by the indexing model from the issue text.

Description

I'm developing a Angular/ASP.NET MVC based NopCommerce plugin. In order for it to load within the host, it must be built as a netcoreapp2.2 Class Library. Unfortunately, I am unable to use node.js tools for Visual Studio 2019. Right-clicking on my package.json file doesn't display the restore packages option, nor is the node_modules package folder with the node.js icon.

I checked my installed workloads and everything was properly installed. I figured I might need to install an additional component, so I searched ad encountered Node.js tools for Visual Studio (https://visualstudio.microsoft.com/vs/features/node-js/) and clicked the Download Visual Studio button which installed the release version. The web page failed to make it clear that it was already included as a workload. So I wasted more time downloading and installing something I already had. Not to disappointment, Microsoft's documentation lead me to a usual dead end.

Well, hours later, I still can't get it to work at all. I suspect it doesn't work with Library projects. Correct? If so, how do I enable it?

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.