style: sort imports with prettier

[larsrickert]

closes #519

• Add prettier plugin to sort imports (in the same way VSCode does it).

[changeset-bot]

⚠️ No Changeset found

Latest commit: ef5fc91

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

[JoCa96]

Is there a benefit over using the default eslint rule https://eslint.org/docs/latest/rules/sort-imports ?
The eslint rule also seems to work with .vue files

[larsrickert]

Is there a benefit over using the default eslint rule https://eslint.org/docs/latest/rules/sort-imports ? The eslint rule also seems to work with .vue files

Yes because eslint use custom rules to sort the imports and you can not configure it to sort exactly like VSCode / Typescript language server which causes conflicts if you have enabled VS Code to also sort imports.

prettier-plugin-organize-imports uses theorganizeImports feature of the TypeScript language service API which is 1:1 what VS Code uses under the hood

[JoCa96]

the referenced issue has been closed, we can update the dependency:

closes #519

* Add prettier plugin to sort imports (in the same way VSCode does it).

* currently this does not work with `.vue` files because we would need to install a deprecated dependency which I don't want to install :) Once this is fixed in [Volar packages renamed simonhaenisch/prettier-plugin-organize-imports#98](https://github.com/simonhaenisch/prettier-plugin-organize-imports/issues/98), we should be able to just update the `prettier-plugin-organize-imports` dependency without any change on our side