Package manager

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

Homebrew/livecheck provides various automated ways of detecting formulae updates.

Repology provides an API that provides details on whether a Homebrew package is outdated e.g. https://repology.org/metapackage/boost/versions

A separate Ruby application that can be trivially deployed on e

My composer.json:

{
    "require": {
    }
}

Output of composer diagnose:

$ sudo php7.4 /usr/local/bin/composer diagnose
Do not run Composer as root/su

This is a great issue to work on if you are new to the Poetry code base and want to start contributing. Over the years the poetry code base has added various fixes that catered to now unsupported versions of python. With the release of 1.2, we will drop support for all Python versions prior to 3.6. With this we want to clean up the code base of any such workarounds we did to support backwards

My proposal is to add the method version() to tools.Git. Calling this method would return the Major.Minor.Patch of the found git executable (maybe as a named tuple). These can be used to customize the git commands which are used. As an example, partial cloning (cloning only some files/directories from a repo to save time) is available since Git 2.19.0. If the executable is new enough, partial clon

Current Behavior:

When I do npm init in a folder with spaces, for example test foo bar, only the first space gets replaced by a dash in the proposed name

Expected Behavior:

All the spaces in the name of the folder should get replaced by a dash

Steps To Rep

In a project with a given tool installed locally (in this case, ember-cli)—

• Expected:

  $ volta list
  
  ⚡️ Currently active tools:
  
      Node: v12.16.2 (current @ /Users/chris/dev/test/foo/package.json)
      Yarn: v1.22.4 (current @ /Users/chris/dev/test/foo/package.json)
      Tool binaries available:
          ember (current @ /Users/chris/dev/test/f

Self-service

• I'd be willing to implement a fix

Describe the bug

The documentation for YN0019 states that

Running yarn cache clean will cause Yarn to try to figure out which packages from the cache aren't referenced by the current lockfile.

Which isn't correct. Running yarn cache clean simply del

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

ref: rubygems/bundler#5263

If a gem is specified via source::path and source::gemspec both with :path => '.', bundler will print

There was an error parsing `Gemfile`: You cannot specify the same gem twice coming from different sources.
You specified that $GEM_NAME (>= 0) should come from source at `.` and source at `.`
. Bundler cannot continue.