`yarn install` warns of three dev dependencies whose peers the repository pins below what they require

Aberta Para iniciantes
  • Algo errado?
#522 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 12 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
76/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
eslint, typescript
Domínio
build-system, tooling

Direção de pesquisa

Comece por package.json no commit indicado e compare as versões fixadas das dependências de desenvolvimento com os intervalos de peers listados na issue. Execute yarn install para confirmar os três avisos YN0060. O trabalho estará concluído quando as versões das dependências satisfizerem os requisitos de seus peers e a instalação terminar sem esses avisos.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Before submitting a new issue
  • I tested using the latest version of the library, as the bug might be already fixed.
  • I tested using a supported version of react native.
  • I checked for possible duplicate issues, with possible answers.
Bug summary

Every yarn install in the repository ends Done with warnings, with three YN0060 lines, one for each dev dependency whose peer package.json pins below what that peer requires.

Peer the repository pins Requested by Requests Newest that accepts the pin
eslint ^9.30.1 (9.36.0) @eslint/js ^10.0.1 eslint ^10.0.0 @eslint/js 9.x, or eslint 10
release-it ^20.2.1 (20.2.1) @release-it/conventional-changelog 10.0.1 ^18.0.0 || ^19.0.0 @release-it/conventional-changelog 12.0.2 (^18 || ^19 || ^20 || ^21)
typescript ~6.0.3 (6.0.3) typescript-eslint ^8.40.0 (8.46.0) >=4.8.4 <6.0.0 typescript-eslint 8.72.1 (<6.1.0)
Library version

main at 2421ea7 (0.0.0-nightly.2421ea7)

Environment info
System:
  OS: Windows 11 10.0.26300
  CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor          "
  Memory: 155.26 GB / 255.67 GB
Binaries:
  Node:
    version: 26.12.1
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 4.9.2
    path: C:\Users\<user>\AppData\Roaming\npm\yarn.CMD
  npm:
    version: 12.2.1
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "33"
      - "35"
      - "35"
      - "35"
      - "36"
      - "37"
    Build Tools:
      - 35.0.0
      - 36.0.0
      - 36.1.0
      - 37.0.0
    System Images:
      - android-26 | Google APIs Intel x86_64 Atom
      - android-28 | Google APIs Intel x86_64 Atom
      - android-29 | Google APIs Intel x86_64 Atom
      - android-30 | Google APIs Intel x86_64 Atom
      - android-31 | Google APIs Intel x86_64 Atom
      - android-32 | Google APIs Intel x86_64 Atom
      - android-33 | Google APIs Intel x86_64 Atom
      - android-34 | Google APIs Intel x86_64 Atom
      - android-35 | Google APIs Intel x86_64 Atom
      - android-36.1 | Google Play Intel x86_64 Atom
      - android-36.1 | Pre-Release 16 KB Page Size Google Play Intel x86_64 Atom
      - android-37.0 | Google APIs Intel x86_64 Atom
    Android NDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-262.9437.185.2621.16467767
  Visual Studio: Not Found
Languages:
  Java:
    version: 17.0.20.1
    path: C:\Program Files\Microsoft\jdk-17.0.20.101-hotspot\bin\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.2.3
    wanted: 19.2.3
  react-native:
    installed: 0.86.3
    wanted: 0.86.3
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
Steps to reproduce
  1. Clone the reproducer branch, which is main at 2421ea7 as it stands: 
    git clone --branch repro/522-dev-dependencies-unmet-peers https://github.com/YevheniiKotyrlo/react-native-css
cd react-native-css
  2. Run yarn install.

Expected: yarn install finishes with no peer warnings, each dev dependency at a version that accepts the peer the repository pins.

Actual: it ends Done with warnings, with a YN0060 line for each of eslint, release-it and typescript.

The run's output on main at 2421ea7, Windows 11, Node 26.12.1, Yarn 4.9.2 
➤ YN0000: · Yarn 4.9.2
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ eslint is listed by your project with version 9.36.0 (p2e483), which doesn't satisfy what @eslint/js and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ release-it is listed by your project with version 20.2.1 (pfd187), which doesn't satisfy what @release-it/conventional-changelog requests (^18.0.0 || ^19.0.0).
➤ YN0060: │ typescript is listed by your project with version 6.0.3 (p806a6), which doesn't satisfy what typescript-eslint and other dependencies request (>=4.8.4 <6.0.0).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 386ms
➤ YN0000: ┌ Link step
➤ YN0007: │ lefthook@npm:2.1.9 must be built because it never has been before or the last one failed
➤ YN0007: │ @tailwindcss/oxide@npm:4.1.13 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.45.1 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 5s 489ms
➤ YN0000: · Done with warnings in 6s 81ms
Reproducible example repository

https://github.com/YevheniiKotyrlo/react-native-css/tree/repro/522-dev-dependencies-unmet-peers

Linguagem predominante
TypeScript
Estrelas
166
Forks
45
Merge médio
17d 22h
PRs com merge (30d)
3

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nativewind/react-native-css

Todas as issues de nativewind/react-native-css

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.