Paul Ebose
Paul Ebose
This is what #1724 looks like: https://github.com/CodeEditApp/CodeEdit/assets/49006567/5e9a5b42-8f6c-4d56-b6b9-67917bfcba77
Yes it does. They are both minor changes.
I also get this error when using `v7.0.0-alpha.20`. Upgrading to `7.0.0-alpha.22` does not show this error.
Just some helpful info: - `@typescript-eslint/parser` and `@typescript-eslint/eslint-plugin` packages are not needed when using `typescript-eslint`. See https://typescript-eslint.io/packages/typescript-eslint - `eslint-plugin-react` now has a merged PR for eslint v9 support. https://github.com/jsx-eslint/eslint-plugin-react/pull/3759 -...
Here is a working config. The caveat is that `npm install` errors because of a dependency conflict. The `--force` flag works fixes it. yarn and pnpm shows a warning. ```ts...
Okay, I'll make those changes now
For the recent changes in #697, I was thinking `pnpm exec` may be better than `pnpx` (pnpm dlx) since it uses the locally installed packages. https://pnpm.io/cli/exec#examples
I checked the source code, the option is only available as a CLI flag
Replaced [`eslint-plugin-import`](https://github.com/import-js/eslint-plugin-import) with [`eslint-plugin-import-x`](https://github.com/un-ts/eslint-plugin-import-x) as it supports eslint v9. It also has an additional rule [`no-rename-default`](https://github.com/un-ts/eslint-plugin-import-x/blob/master/docs/rules/no-rename-default.md) under [Helpful warnings](https://github.com/un-ts/eslint-plugin-import-x#helpful-warnings) section.
@PatrykKuniczak The conflicts have now been resolved