Skip to content
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.

Sign up for GitHub

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

Jump to bottom

@graphql-codegen/visitor-plugin-common@npm:4.1.0: No candidates found #9808

Open
efstathiosntonas opened this issue Jan 9, 2024 · 2 comments
Open

@graphql-codegen/visitor-plugin-common@npm:4.1.0: No candidates found #9808

efstathiosntonas opened this issue Jan 9, 2024 · 2 comments

Comments

@efstathiosntonas
Copy link

efstathiosntonas commented Jan 9, 2024 •
edited

Which packages are impacted by your issue?

@graphql-codegen/visitor-plugin-common

Describe the bug

Cannot install using yarn@4 because @graphql-codegen/visitor-plugin-common@4.1.0 is missing from registry.

Your Example Website or App

none

Steps to Reproduce the Bug or Issue

  1. try to install packages of package.json listed below
  2. fails with: @graphql-codegen/visitor-plugin-common@npm:4.1.0: No candidates found
  3. npmjs.com still got the 4.0.1 version

Expected behavior

install the plugin

Screenshots or Videos

No response

Platform

  • OS: macOS
  • NodeJS: 18.17.1
  • graphql version: 16.3.0
  • @graphql-codegen/* version(s): 5.0.0

Codegen Config File

No response

Additional context

If I manually install it yarn add @graphql-codegen/visitor-plugin-common on top of the package.json below it installs just fine, it installs 4.0.1 since 4.1.0 is missing from npmjs.com registry.

package.json:

    "@graphql-codegen/add": "^5.0.0",
    "@graphql-codegen/cli": "^5.0.0",
    "@graphql-codegen/fragment-matcher": "^5.0.0",
    "@graphql-codegen/introspection": "^4.0.0",
    "@graphql-codegen/jsdoc": "^3.0.0",
    "@graphql-codegen/typescript": "^4.0.1",
    "@graphql-codegen/typescript-apollo-client-helpers": "^3.0.0",
    "@graphql-codegen/typescript-operations": "^4.0.1",
    "@graphql-codegen/typescript-react-apollo": "^4.1.0",
@efstathiosntonas
Copy link
Author

It seems that by adding

npmRegistryServer: https://registry.npmjs.org

into .yarnrc.yml it fixes the issue. I guess that since 4.1.0 is not marked as latest on npmjs registry.yarnpkg.com fails to pick it up? 🤔

@Tobbe
Copy link

Tobbe commented Jan 12, 2024

Seems like this is the commit that introduce the new version dependency that yarn can't find
eaa3d60

@jtoar jtoar mentioned this issue Jan 17, 2024
Merged
jtoar added a commit to redwoodjs/redwood that referenced this issue Jan 17, 2024
@jtoar
chore(fwtools): handle existing resolutions in tarsync (#9840)
c9426e3 
Currently there's a `@graphql-codegen` package in canary that doesn't
exist at the published version we have to set a resolution for (see
dotansimha/graphql-code-generator#9808). `yarn
rwfw project:tarsync` overwrites the resolutions, so you have to add it
back after running the command which is annoying. This just makes it add
the tarball resolutions to the existing ones:

```json5
  "resolutions": {
    // This is now preserved
    "@graphql-codegen/visitor-plugin-common": "4.0.1",
    "@redwoodjs/fastify-plugin-streaming": "./tarballs/redwoodjs-fastify-plugin-streaming.tgz",
    "@redwoodjs/api": "./tarballs/redwoodjs-api.tgz",
    "@redwoodjs/api-server": "./tarballs/redwoodjs-api-server.tgz",
    // ...
  }
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Tobbe @efstathiosntonas