chore(eslint-config-next): bump eslint-import-resolver-typescript (#43010)
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> ## Bug Bumps `eslint-import-resolver-typescript` in `eslint-config-next` to the latest version to pick up a fix from `3.1.0`. As mentioned here, https://github.com/import-js/eslint-import-resolver-typescript/issues/107, the typescript parser is unable to resolve the `typesVersions ` field in their `package.json`. An example repo using this is [`@vercel/examples-ui`](https://github.com/vercel/examples/blob/385a2e968619f9e50f488e2857e021841ae61030/packages/ui/package.json#L14-L22) which will report an eslint `import/no-unresolved` error when using the previous version of `eslint-import-resolver-typescript` (see https://github.com/import-js/eslint-import-resolver-typescript/issues/107). This was fixed in https://github.com/import-js/eslint-import-resolver-typescript/pull/110 This can be locally fixed by bumping `>=eslint-import-resolver-typescript@3.1.0` but decided it should be resolved here too. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [x] Errors have a helpful link attached, see `contributing.md` Closes: https://github.com/vercel/next.js/pull/41786Co-authored-by:JJ Kasper <jj@jjsweb.site>
Showing
This diff is collapsed.
This diff is collapsed.
Please
register
or
sign in
to comment