chore(deps): update dependency synckit to ^0.8.3 for yarn PnP

[hanseo0507]

I updated dependency sycnkit to from ^0.8.1 to ^0.8.3.
This is because synckit@^0.8.1 breaks using this pugin with Yarn PnP in VSCode.

This issue has already been reported(#164), and has been resolved in synckit(un-ts/synckit#98), but this plugin dependency has not been updated

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4faa186

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[JounQin]

You can upgrade synckit on your side manually AFAIK?

[hanseo0507]

How can i upgrade synckit manually?

[JounQin]

How can i upgrade synckit manually?

1. yarn upgrade synckit
2. yarn remove eslint-import-resolver-typescript && yarn add -D eslint-import-resolver-typescript
3. rm -rf yarn.lock && yarn
4. Edit yarn.lock file, remove synckit@^0.8.1 section, and run yarn

[hanseo0507]

I am testing in the Yarn Berry Monorepo environment.
As you said, I found a way to manually update directly from Yarn berry, and I executed it.

yarnPath: .yarn/releases/yarn-3.2.1.cjs
packageExtensions:
  'eslint-import-resolver-typescript@^3.4.0':
    dependencies:
      synckit: '^0.8.3'

Isn't it impossible to use it in Yarn PnP environment unless you upgrade it manually?

[JounQin]

Isn't it impossible to use it in Yarn PnP environment unless you upgrade it manually?

I tried in https://github.com/kriasoft/react-starter-kit, it seems true, so this PR is accepted.

In my imagine, when I remove "synckit@npm:^0.8.1" section in yarn.lock, yarn should reinstall the latest version of synckit, but it seems not true.

[JounQin]

#169 (comment)

[JounQin]

@hanseo0507 Thanks for your contribution!

[hanseo0507]

@JounQin Thank you for reviewing my PR.
How many days will it take for this PR to be reflected in the release?

[JounQin]

@JounQin Thank you for reviewing my PR. How many days will it take for this PR to be reflected in the release?

Right now.

[hanseo0507]

@JounQin Thank you for reviewing my PR. How many days will it take for this PR to be reflected in the release?

Right now.

Okay. Thank you!

[JounQin]

@hanseo0507

[email protected] has been released! Thanks for your contribution again!

[noahnu]

For future reference, if using Yarn Modern, you can update a transitive dependency like synckit by running yarn up -R synckit. The newly released version matches the semantic version range ^0.8.1, so running yarn up -R synckit will bump the resolved version to the latest matching that range.