ENOWORKSPACES when publishing from workspace
Description
Publishing one of the packages from a workspace like packages/react-scripts in a create-react-app fork leads to a ENOWORKSPACES error when running the npm config get registry command:
$ np --yolo
✖ Error: Command failed with exit code 1: npm config get registry
npm ERR! code ENOWORKSPACES
npm ERR! This command does not support workspaces.
npm ERR! A complete log of this run can be found in: /Users/k/.npm/_logs/2023-09-13T12_57_00_983Z-debug-0.log
at makeError (file:///Users/k/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/execa/lib/error.js:59:11)
at handlePromise (file:///Users/k/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/execa/index.js:124:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Module.getRegistryUrl (file:///Users/k/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/np/source/npm/util.js:154:19)
at async ui (file:///Users/k/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/np/source/ui.js:129:22)
at async file:///Users/k/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/np/source/cli-implementation.js:137:18This is a regression since a few months - in April / May 2023 we were able to publish these packages without problems.
Steps to reproduce
np --yoloornpin a package inside of a workspace
Expected behavior
np works in a package inside of a workspace without errors
Environment
np - 8.0.4
Node.js - 18.17.1
npm - 9.6.7
Git - 2.39.2
OS - macOS Ventura 13.5.2
sindresorhus / np
A better `npm publish`
7.6k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too