dotnet / dotnet/sdk

Ability to specify another package manager for JavaScript SDK projects

Open
#44,516 7 comments 18 reactions 1 assignee Claimed by @joj View on GitHub
Area-esproj untriaged
Dominant language
C#
Stars
3.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

Sorry if this is the wrong place but coming from this https://github.com/dotnet/aspnetcore/discussions/56111 discussion since the JavaScript.SDK currently isnt a public project.

### Is your feature request related to a problem? Please describe.

An option to set a package manager other than `npm` when using `Microsoft.VisualStudio.JavaScript.SDK` for example `pnpm`. This would also be ideal if we want to specify any extra arguments for install such as being able to run `npm ci` condtionally for CI builds.

This would also potentially allow us to use deno.

### Describe the solution you'd like

Much like the other properties in the `esproj` type it would probably be prefereable to have a similar interface to how the builds and start commands work.

```xml


pnpm install
pnpm-lock.yaml

```

### Additional context

Currently there is a workaround for this by installing the SDK's .props and .targets outside of the `` and move it into `` to avoid the `.targets` being imported after the override due to ![Image](https://github.com/user-attachments/assets/dfa172fc-bd51-4e66-97fd-2be14246af51)

```xml




$(PackageJsonDirectory)pnpm-lock.yaml











```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.