-
Notifications
You must be signed in to change notification settings - Fork 179
Issues: nodejs/corepack
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
COREPACK_ENABLE_AUTO_PIN should be possible to set on a project level
#628
opened Feb 3, 2025 by
SimonMorkSaetre
Please don't make error of fetching latest version information if packageManager field is specified.
#625
opened Feb 3, 2025 by
anatawa12
Expand packageManager description with allowed & recommended hash values
#620
opened Jan 31, 2025 by
MikeMcC399
corepack use
in monorepo targets root not project package.json
#607
opened Jan 21, 2025 by
MikeMcC399
ci vitest fails "handle integrity checks" on Windows Node.js 23
#597
opened Jan 14, 2025 by
MikeMcC399
Corepack should not download package manager if binary is available
#586
opened Dec 24, 2024 by
trivikr
Implement devEngines proposal from Package Metadata Interoperability Collab Space
#567
opened Oct 8, 2024 by
trivikr
Feature request:
COREPACK_NPM_REGISTRY
defaults to $(npm config get registry)
#540
opened Jul 19, 2024 by
zanminkian
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.