npm workspaces "WARN: some-package-name in filter set, but no workspace folder present"

Question

I have a repo with many npm packages inside, using npm workspaces

The top-level package.json contains the line:

  "workspaces": [
    "*"
  ]

When I run npm i -ws or other npm commands, I receive the warning:

WARN: some-package-name in filter set, but no workspace folder present

I'm not quite sure what the message means - I think the 'filter set' is the -w option, but the workspace folder some-package-name definitely exists.

One note is that the some-package-name/package.json contains an org prefix, eg:

"name": "@mycompany/some-package-name",

So maybe that's the cause. I can't rename the folder from some-package-name to @mycompany/some-package-name though as I'm concerned a directory starting with @ may break things.

What does the warning mean and how can I resolve it?

running the command twice worked for me somehow

derpedy-doo
– derpedy-doo

2022-12-02 13:29:45 +00:00
Commented Dec 2, 2022 at 13:29 — derpedy-doo
– derpedy-doo, Commented Dec 2, 2022 at 13:29

Valentine Shi · Accepted Answer · 2024-11-13 14:30:15Z

8

I ran into the same problem, using the name configured in the workspace's package instead of the folder name fixed the issue for me, even with an @.

npm install --workspace=@mycompany/some-package-name

The issue may appear for the package in question package.json and package-lock.json name fields do not match the workspace folder naming and package name and / or each other.

The command updated both name fields so that the warning is gone.

edited Nov 13, 2024 at 14:30

Valentine Shi

8,0894 gold badges60 silver badges50 bronze badges

answered Mar 11, 2022 at 1:37

Kusmeroglu

3012 silver badges3 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

mikemaccana Over a year ago

I think that was the cause of my problem too. Essentially - and what I didn't understand - was that -ws stands for all workspaces. -w means a single workspace.

kukuruznik · Accepted Answer · 2023-04-09 13:20:22Z

7

I have run into the same problem recently with my monorepo: the reason was that the project's name (without the scope) in package.json did not match the name of the directory (subproject) it was stored within.

If the subprojects of the monorepo are stored within a packages directory in the project root and the root package.json contains

"workspaces": [
    "packages/*"
]

then npm expects a subproject named @<scope>/project-name to be in the directory packages/project-name.

answered Apr 9, 2023 at 13:20

kukuruznik

1261 silver badge6 bronze badges

1 Comment

Jason Over a year ago

I seem to be getting the same error regardless of whether I make an @scope/module_name directory or just a module_name directory Edit: Turns out if you were faking workspaces by putting a 'node_modules' directory in the path, npm workspaces does not like it, and you have to remove that

foxtdev · Accepted Answer · 2025-05-31 12:46:53Z

3

For me, the issue seemed to be that I had "private": true in my workspace root package json & some of the individual workspace package JSONs. After removing it, the issue seemed to go away. I'm not entirely sure why this is the case it seems unintuitive to me, but there's probably a good reason for it.

answered May 31 at 12:46

foxtdev

3182 silver badges18 bronze badges

Comments

Dave Stewart · Accepted Answer · 2022-10-07 16:54:31Z

1

I have a slightly different answer.

I'm creating a package.json programatically, using Fs.writeFileSync('./path/to/package.json').

I run npm install -w=workspace foo bar immediately after, but it seems that this fails sometimes; NPM somehow hasn't picked up on the file, as if I run the same command twice, the second one always works.

Adding a small delay using setTimeout() also works, though I feel a bit dirty having had to do this; I don't know if this is an issue with Node or my lack of knowledge around Node's process lifecycle.

Anyway, in this case – and in lieu of better solution – it works.

answered Oct 7, 2022 at 16:54

Dave Stewart

2,5642 gold badges25 silver badges26 bronze badges

1 Comment

mikemaccana Over a year ago

fs.writeFileSync() should block until complete. However some operating systems acknowledge writes before they've actually happened.

Raman · Accepted Answer · 2024-05-19 19:27:32Z

1

For me I was getting this warning/issue when I was using monorepo using turborepo, created using command - npx create-turbo@latest.

I was getting the error because I changed the name of the nextjs project. But I didn't change the name property in package.json. When name property was changed to name of the folder/package, issue was resolved.

Once you change the name property in package.json, make sure you re-install the tailwind or any other packages you were installing. It will not prompt the above error.

Refer to the below image: the name of the package/project is user-app but in the package.json name is web, I edited this name to user-app and the issue was resolved.

edited May 19, 2024 at 19:27

answered May 1, 2024 at 4:49

Raman

112 bronze badges

1 Comment

mikemaccana Over a year ago

Have an upvote. But please include the text instead of images, that way your answer will appear when people search.

Gianluca Casati · Accepted Answer · 2022-10-08 13:13:07Z

0

I solved this issue using a file: dependency as "recommended by npm" (read below).

Actually many articles say that npm recommends to use file: to reference a dependency between two workspace packages (and then often they use the asterisk anyway) but honestly I did not found that hint in npm docs, but it works! ... at least it worked for me, using the following

Explicitly list the workspaces

So instead of using an asterisk I have, for example

  "workspaces": [
    "packages/models",
    "packages/database",
    "webapp"
  ]

I also have a scoped package name

for instance

  "name": "@project/models",
  "private": "true"

I am using "file:" dependencies

Instead of

  "dependencies": {
    "@project/models": "*"
  }

I use file:WORKSPACE_PATH

  "dependencies": {
    "@project/models": "file:packages/models"
  }

edited Oct 8, 2022 at 13:13

answered Jul 13, 2022 at 9:48

Gianluca Casati

3,8411 gold badge37 silver badges25 bronze badges

5 Comments

Dave Stewart Over a year ago

You say "as recommended by npm"; do you have a link to any documentation?

Gianluca Casati Over a year ago

@DaveStewart it is quoted and immediately below I wrote that I found no reference to that in official npm docs but I found few articles googling that mentioned it, that is why I am sharing what I found out. I hope that my message is more clear now.

Dave Stewart Over a year ago

OK, I just got this working, but I had to use a relative path from the workspace package file: "@tools/web-tools": "file:../../tools/web-tools"... and – of course – run npm install from the root again.

towry Over a year ago

I believe using 'file:' is a legacy way to do monorepo.

Samuel Lindblom Over a year ago

Indeed. Each workspaces should have a symlink in the root node_modules that the other workspaces can use to declare proper dependencies, so that you don't have to use file dependencies.

Collectives™ on Stack Overflow

npm workspaces "WARN: some-package-name in filter set, but no workspace folder present"

6 Answers 6

1 Comment

1 Comment

Comments

1 Comment

1 Comment

Explicitly list the workspaces

I also have a scoped package name

I am using "file:" dependencies

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

1 Comment

1 Comment

Comments

1 Comment

1 Comment

Explicitly list the workspaces

I also have a scoped package name

I am using "file:" dependencies

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related