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

[Bug] Cannot install typescript@next #1844

Closed
1 task
FallingSnow opened this issue Sep 18, 2020 · 8 comments
Closed
1 task

[Bug] Cannot install typescript@next #1844

FallingSnow opened this issue Sep 18, 2020 · 8 comments
Labels
bug Something isn't working stale Issues that didn't get attention

Comments

@FallingSnow
Copy link

FallingSnow commented Sep 18, 2020

  • I'd be willing to implement a fix

Describe the bug

Berry fails to install typescript@next, but classic yarn succeeds.
Error message: Cannot apply hunk #6

To Reproduce

yarn set version berry
yarn add typescript@next
Reproduction
$ yarn add typescript@next
 YN0000:  Resolution step
 YN0000:  Completed in 0.37s
 YN0000:  Fetch step
 YN0013:  typescript@npm:4.1.0-dev.20200918 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ typescript@patch:typescript@npm%3A4.1.0-dev.20200918#builtin<compat/typescript>::version=4.1.0-dev.20200918&hash=5b02a2 can't be found in the cache and will be fetched from the disk
 YN0013:  typescript@npm:4.1.0-dev.20200918 can't be found in the cache and will be fetched from the remote registry
➤ YN0066: │ typescript@patch:typescript@npm%3A4.1.0-dev.20200918#builtin<compat/typescript>::version=4.1.0-dev.20200918&hash=5b02a2: Cannot apply hunk #6
➤ YN0000: └ Completed in 7.9s
➤ YN0000: Failed with errors in 8.26s

Environment if relevant (please complete the following information):

  • OS: Linux laptop 5.8.5-arch1-1 👑 Say hello to Yarn 2 #1 SMP PREEMPT Thu, 27 Aug 2020 18:53:02 +0000 x86_64 GNU/Linux
  • Node version: v14.8.0
  • Yarn version: 2.2.2
@FallingSnow FallingSnow added the bug Something isn't working label Sep 18, 2020
@arcanis
Copy link
Member

arcanis commented Sep 18, 2020

TypeScript 4.0.3 is currently being released, so we'll update the patch in our next minor (next week or so, but you'll be able to use master as soon as this issue is closed).

@FallingSnow
Copy link
Author

Great! Thank you!

fyi Typescript 4.0.3 has been released.

@SagnikPradhan
Copy link
Contributor

I feel sad for @arcanis, he has to constantly fix his patch for typescript. Waiting for the day when typescript supports pnp natively.

@yarnbot
Copy link
Collaborator

yarnbot commented Oct 24, 2020

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

@yarnbot yarnbot added the stale Issues that didn't get attention label Oct 24, 2020
@arcanis
Copy link
Member

arcanis commented Oct 24, 2020

Closing since it should now be fixed in master.

@arcanis arcanis closed this as completed Oct 24, 2020
@LvChengbin
Copy link

I encountered the same problem while installing typescript version 4.2.2.

@ericvera
Copy link

@arcanis where can I check if the patch is available?

@merceyz
Copy link
Member

merceyz commented Feb 24, 2021

See #2514 (comment)

@yarnpkg yarnpkg locked as resolved and limited conversation to collaborators Feb 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working stale Issues that didn't get attention
Projects
None yet
Development

No branches or pull requests

7 participants