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

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
        

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 test suite has grown significantly, this means that there is significant amount of code duplication in-efficient

If you are submitting a pull request associated with this, please keep the pull requests small and modular. This means, do not do too much in one PR and

• /pnpm/packages/audit - #2862
• /pnpm/packages/package-store a86209b67fccc37c5b017dd9ce61d2b3f9a55789
• /pnpm/packages/cafs #2867
• /pnpm/packages/client pnpm/pnpm#2877
• /pnpm/packages/fetch pnpm/pnpm#2878
• /pnpm/packages/filter-lockfile #2887
• /pnpm/packages/filter-workspace-packages #2887
• /pnpm/packages/

Conan can't work on OpenBSD.

ERROR: Invalid setting 'OpenBSD' is not a valid 'settings.os' value.
Possible values are ['AIX', 'Android', 'Arduino', 'Emscripten', 'FreeBSD', 'Linux', 'Macos', 'Neutrino', 'SunOS', 'Windows', 'WindowsCE', 'WindowsStore', 'iOS', 'tvOS', 'watchOS']

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

• 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'

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

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

Currently spack does not support the following packages, all of these packages are installed outside of Spack at Cori, we would like to get support for these packages if possible.

• cpmd https://www.lcrc.anl.gov/for-users/software/available-software/cpmd/
• ComputeCPP https://github.com/codeplaysoftware/computecpp-sdk need to confirm link
• ds9 https://sites.google.com/cfa.harvard.