package-json-upgrade icon indicating copy to clipboard operation
package-json-upgrade copied to clipboard

Results 20 package-json-upgrade issues
Sort by recently updated
recently updated
newest added

Right now the plugin is visible in the merge editor. A suggestion is to hide it in that place.

What I see currently: ``` "@types/node": "^14.17.26", Update available: 18.11.7 "@types/node": "~14.17.26", Update available: 18.11.7 ``` What I'd like to see: ``` "@types/node": "^14.17.26", Update available: 18.11.7, 14.18.33 "@types/node": "~14.17.26",...

I recently had a need to alias 2 different versions of the same package like this: ```json "snowpack2": "npm:snowpack@2", "snowpack3": "npm:snowpack@3", ``` But as you can see the plugin says...

Hello, I would like to know if it's possible to add a feature that will display every possible update. Major, minor and bugfix instead of only showing the final last...

hi, i have this error what i go to menu vsc osx -> command + p -> "Toggle showing package.json available updates": --> return popup which this error --> command...

It is possible to [configure registries with Yarn](https://yarnpkg.com/configuration/yarnrc#npmRegistryServer). These configurations are not picked up by `package-json-upgrade`. I could technically get this plugin to see my files if I also created...

Hello 👋 Thank you very much for the extension, it's exactly what I was looking for, you did a great job! However, I'm kinda "minimalistic" person and love when my...

Thanks for this extension! I'd like to display updates in pnpm workspace catalogs. There is an issue #43 which is somewhat related. Thought I could take a stab at it:...

It is valid to write `"@types/node": "20.x",`. But currently that will show `(current version not found)` which is obviously not correct.