Skip to content
#

Package manager

A package manager is a set of tools that automates and manages computer software. They deal with packages, or collections, of bundled files. Package managers make it easy to install, upgrade, or remove software for a computer's operating system.

Here are 1,067 public repositories matching this topic...

sabrinaluo
sabrinaluo commented Jun 5, 2019

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

  1. install a package with any version, e.g "pkg": "^1.0.0"
  2. add resolutions field in package.json, pkg: "1.0.0"
  3. upd
Dropa
Dropa commented Sep 24, 2019

So if you happen to insert invalid version string when requiring package, it will still write it into composer.json and nothing works after that. So for example; composer require phpunit/phpunit:"8.3.3 as ^8.3"

My composer.json:

{
    "require": {
        "phpunit/phpunit": "8.3.3 as ^8.3"
    }
}

Output of composer diagnose:

$ composer diagnose
        
pnpm
athens
arschles
arschles commented Nov 13, 2019

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

Not related to a problem

Describe the solution you'd like

We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.

_Edit from @arschles - we have focused this issue to just the twitte

berry
mrtnbroder
mrtnbroder commented Sep 21, 2020
  • I'd be willing to implement this feature
  • This feature can already be implemented through a plugin

Describe the user story

I was looking into patch and how it works, but the docs didnt give much info. The CLI also didnt. I had to look around to get an idea of it. I thought it worked similar like patch-package. However, it works differently.

**Describe the solution you'

chriskrycho
chriskrycho commented Apr 16, 2020

The design for volta list specified that we would output both the default version from the user's toolchain and the version set in a local package:

$ volta list all --format=plain
runtime node@v12.2.0
runtime node@v11.9.0
runtime node@v10.15.3 (default)
runtime node@v8.16.0 (current @ ~/node-only/package.json)

We currently only print the (current @ ...) when in a package

Wikipedia
Wikipedia
You can’t perform that action at this time.