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

• I am on the latest Poet

Hello,

It seems that the default profile is mandatory in 2.0, even though the error message implies otherwise.

Environment Details (include every applicable attribute)

• Conan version: 2.0.0a2

Steps to reproduce (Include if Applicable)

• remove default profile
• run conan create --profile=whatever

Logs (Executed commands with output) (Include/Attach if Applicab

Hooks for scopes get a double prefix, ie @@scope, when shown with the npm hook ls command. This is due to the response from the web request already including the prefix in the name field, and the following lines of code then locally adding the prefix again, duplicating it.

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.

• I'd be willing to implement this feature (contributing guide)
• This feature is important to hav

Describe the bug
CodeQL show that we are logging paths directly. We should instead escape and then log them.

To Reproduce
Results are shown here: https://github.com/gomods/athens/pull/1748/checks?check_run_id=4567576462

Expected behavior

We can simply log escaped paths provided by net/url: https://pkg.go.dev/net/url#URL.EscapedPath

Additional context
Add an

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.

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