yarn dlx @yarnpkg/doctor in monorepo gives isn't supported by any available resolver error for child packages

[scottdickerson]

I have a pretty standard monorepo and am trying to verify that my packages are not missing any dependencies. I'm using yarn v3 and pnp. Here's an example package.json section pointing to devDependencies

  "devDependencies": {
        "@emotion/css": "11.10.0",
        "@testing-library/dom": "8.18.0",
        "@testing-library/react": "13.4.0",
        "@testing-library/user-event": "14.4.3",
        "@types/jest": "29.0.3",
        "@types/react": "18.0.20",
        "jest-axe": "6.0.0",
        "react": "18.2.0",
        "react-dom": "18.2.0"
    }

Here's my .yarnrc.yml

npmScopes:
  my_custom_scope:
    npmAuthToken: '<my token>'
    npmPublishRegistry: 'https://npm.pkg.github.com/'
    npmRegistryServer: 'https://npm.pkg.github.com/'

plugins:
  - path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
    spec: '@yarnpkg/plugin-workspace-tools'

yarnPath: .yarn/releases/yarn-3.2.3.cjs

Here's the output of the yarn dlx command

➜  yarn dlx @yarnpkg/doctor
➤ YN0000: ┌ Resolution step
➤ YN0060: │ @yarnpkg/plugin-interactive-tools@npm:4.0.0-rc.20 [c9c68] provides react (p9163f) with version 16.14.0, which doesn't satisfy what ink and some of its descendants request
➤ YN0060: │ @yarnpkg/plugin-version@npm:4.0.0-rc.20 [c9c68] provides react (p011dc) with version 16.14.0, which doesn't satisfy what ink and some of its descendants request
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 2s 207ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 231ms
➤ YN0000: Done with warnings in 2s 600ms

➤ YN0000: Found 1 package(s) to process
➤ YN0000: For a grand total of 4 file(s) to validate

➤ YN0000: ┌ /Users/scottdickerson/Documents/GitHub/skeletor/packages/buttons/package.json
➤ YN0000: │ User scripts prefixed with "pre" or "post" (like "prebuild") will not be called in sequence anymore; prefer calling prologues and epilogues explicitly
➤ YN0000: │ Resolving @emotion/css@11.10.0 errored with @emotion/css@11.10.0 isn't supported by any available resolver
➤ YN0000: │ Resolving @testing-library/dom@8.18.0 errored with @testing-library/dom@8.18.0 isn't supported by any available resolver
➤ YN0000: │ Resolving @testing-library/react@13.4.0 errored with @testing-library/react@13.4.0 isn't supported by any available resolver
➤ YN0000: │ Resolving @testing-library/user-event@14.4.3 errored with @testing-library/user-event@14.4.3 isn't supported by any available resolver
➤ YN0000: │ Resolving @types/jest@29.0.3 errored with @types/jest@29.0.3 isn't supported by any available resolver
➤ YN0000: │ Resolving @types/react@18.0.20 errored with @types/react@18.0.20 isn't supported by any available resolver
➤ YN0000: │ Resolving jest-axe@6.0.0 errored with jest-axe@6.0.0 isn't supported by any available resolver
➤ YN0000: │ Resolving react@18.2.0 errored with react@18.2.0 isn't supported by any available resolver
➤ YN0000: │ Resolving react-dom@18.2.0 errored with react-dom@18.2.0 isn't supported by any available resolver
➤ YN0000: └ Completed in 0s 339ms
➤ YN0000: ⠹ --------------------------------------------------------------------------------

[emptyflask]

Same, almost two years later.

➤ YN0000: │ Resolving @popperjs/core@^2.11.6 errored with @popperjs/core@^2.11.6 isn't supported by any available resolver
➤ YN0000: │ Resolving @rails/ujs@^7.0.4-1 errored with @rails/ujs@^7.0.4-1 isn't supported by any available resolver
➤ YN0000: │ Resolving @types/react-modal@^3.13.1 errored with @types/react-modal@^3.13.1 isn't supported by any available resolver
➤ YN0000: │ Resolving bootstrap@5.1.3 errored with bootstrap@5.1.3 isn't supported by any available resolver
➤ YN0000: │ Resolving choices.js@^10.2.0 errored with choices.js@^10.2.0 isn't supported by any available resolver
➤ YN0000: │ Resolving classnames@^2.3.2 errored with classnames@^2.3.2 isn't supported by any available resolver
➤ YN0000: │ Resolving date-fns@^3.6.0 errored with date-fns@^3.6.0 isn't supported by any available resolver

I'm guessing this is something that can safely be ignored?

[ajeetshah]

I am also getting these warnings, not sure how to fix it.

➤ YN0000: │ Resolving @emotion/react@^11.10.5 errored with @emotion/react@^11.10.5 isn't supported by any available resolver
➤ YN0000: │ Resolving @reduxjs/toolkit@^1.9.1 errored with @reduxjs/toolkit@^1.9.1 isn't supported by any available resolver
➤ YN0000: │ Resolving axios@^1.2.0 errored with axios@^1.2.0 isn't supported by any available resolver
➤ YN0000: │ Resolving bootstrap@^5.2.3 errored with bootstrap@^5.2.3 isn't supported by any available resolver

[MyNameIsNeXTSTEP]

Why does not anyone from the yarnpkg/berry team looking at this ?

The problem is still present.

Configuration

• Yarn version: 4.5.1
• Dependency provided in both root package.json and one workspace package package.json files: axios ^1.7.7
• Workspace package is listed in the root package.json (no errors about it)
• tsconfig.json of the workspace package extends the root tsconfig.json
• All dependencies were installed in both the root and workspace (specified in both too), and the whole pnp file was regenerated

Executing doctor check with: yarn dlx @yarnpkg/doctor getting this:

• Resolving axios@^1.7.7 errored with axios@^1.7.7 isn't supported by any available resolver for the root package.json
• Resolving axios@^1.7.7 errored with axios@^1.7.7 isn't supported by any available resolver for the workspace package.json

---

Please take this into account and provide some useful feedback @yarnbot