Skip to content

[FEATURE REQUEST] Add JavaScript Package Manager: Yarn (yarn), Performant Node Package Manager (pnpm) And JavaScript Package Manager (jspm) In UniGetUI #3506

Open

Description

@rc-chuah

Please confirm these before moving forward.

  • I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
  • This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template.

Describe the new feature

Can You Add JavaScript Package Manager In UniGetUI Such As: Yarn (yarn), Performant Node Package Manager (pnpm) And JavaScript Package Manager (jspm).

Describe how this new feature could help users

It Will Benefit Lots Of People And Save Time Too.

Activity

  1. josh-hemphill commented on Jul 19, 2025

    @josh-hemphill

    Was hoping the ability to change the executable would help, but pnpm uses a --format flag instead of the --parsable flag that UnigetUI calls with, which means I still don't see any updates for my JS packages 😔

  2. EDM115 commented on Jul 21, 2025

    @EDM115

    the problem with this is that the "Node" ecosystem is very fragmented.
    already 4 major package managers (including NPM), + you can also now handle package updates with runtimes (Deno and Bun)

  3. mrixner commented on Jul 21, 2025

    @mrixner
    Contributor

    Was hoping the ability to change the executable would help, but pnpm uses a --format flag instead of the --parsable flag that UnigetUI calls with, which means I still don't see any updates for my JS packages 😔

    I see no easy way to fix this beyond a rewrite of the npm code to have effectively four subpackage managers that it uses to craft arguments and such.

  4. michmerr commented on Mar 1, 2026

    @michmerr

    Was hoping the ability to change the executable would help, but pnpm uses a --format flag instead of the --parsable flag that UnigetUI calls with, which means I still don't see any updates for my JS packages 😔

    I see no easy way to fix this beyond a rewrite of the npm code to have effectively four subpackage managers that it uses to craft arguments and such.

    Does it have to be supported within the npm package manger, or would it be cleaner to create separate package managers for pnpm, yarn, etc.? They don't conflict with each other in their global scopes, which is where packages installed through UniGetUI would be scoped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

new-featureA new feature that could be useful in WingetUIready-to-go

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions