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.

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

yarn install --frozen-lockfile shows a warning: The engine "vscode" appears to be invalid. #293

Open
2 tasks done
johnferguson-at-nuix opened this issue Jan 4, 2024 · 1 comment

Comments

@johnferguson-at-nuix
Copy link

Describe the bug

During install of dependencies I get a warning about a transitive dependency being wrong:

yarn install --frozen-lockfile
yarn install v1.22.21
warning ../package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
warning [email protected]: The engine "vscode" appears to be invalid.
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
✨  Done in 4.01s.

Upon using the yarn why command this dependency is linked to vite-plugin-checker:

yarn why vscode-languageclient
yarn why v1.22.21
warning ../package.json: No license field
[1/4] 🤔  Why do we have the module "vscode-languageclient"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "[email protected]"
info Reasons this module exists
   - "vite-plugin-checker" depends on it
   - Hoisted from "vite-plugin-checker#vscode-languageclient"
info Disk size without dependencies: "944KB"
info Disk size with unique dependencies: "1.43MB"
info Disk size with transitive dependencies: "2.14MB"
info Number of shared dependencies: 5
✨  Done in 0.16s.

Reproduction

Going into my repository I execute:

  1. git clean -dxf
  2. yarn install --frozen-lockfile

Expected behavior

I am expecting to not get a warning about transitive dependencies brought in by vite-plugin-checker

yarn install --frozen-lockfile
yarn install v1.22.21
warning ../package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
✨  Done in 4.01s.

System Info

System:
    OS: macOS 12.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 73.06 MB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    Yarn: 1.22.21 - ~/.nvm/versions/node/v18.18.2/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm
  Browsers:
    Chrome: 120.0.6099.129
    Safari: 15.1
  npmPackages:
    vite-plugin-checker: ^0.6.2 => 0.6.2

Additional context

This is not a blocker assuming that it doesn't indicate a more serious issue. I noticed this: microsoft/vscode#91009

One poster commented:

In this case it's useless warning and can be ignored.
Unfortunately - only way to hide error specifically for vscode - only all
errors about engine yarn install --ignore-engines

Perhaps this error can be ignored? If so this issue can be closed.

Validations

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
@StijnMaenhautCZ
Copy link

+1 Experiencing the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants