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:

$ npm find-dupes

added 24 packages, removed 1 package, and changed 1 package in 10s

59 packages are looking for funding
  run `npm fund` for details

Expected Behavior:

$ npx npm@6 find-dupes
move	source-map	0.5.7	node_modules/@babel/core/node_modules/source-map		node_modules/tap/node_modules/@babel/core/node_modules/source-map
move	@babel/

Hi,

I just realized there is no update/upgrade section in your doc. It could be nice to have clear command on how to update the software, specially if there is some breaking changes or whatever.

Self-service

• I'd be willing to implement a fix

Describe the bug

Yarn berry doesn't download Git LFS files for packages. Yarn v1 does.

To reproduce

yarn v1 works:

mkdir yarn1; cd yarn1
yarn add https://github.com/signalapp/better-sqlite3
ls -lah node_modules/better-sqlite3/deps/sqlite3.tar.gz
# -rw-r--r--  1 kishan  staff    18M Apr 28 00:18 node_modul

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.

Could it be possible to have a warning message when installing a rock that contains a module that is already provided by another rock? Or is there already an option for this and I didn't find it?

At least with Luarocks version 3.2.1 I verified that there are no warnings for this case.

However it seems that Luarocks is aware of the collision and installs the new module under another name and