Azat S.

Thank you for your issue! This feature was implemented in 96cfcd8be3dee5870a14de1736e76af7632cc8b0 and released in [v3.0.0](https://github.com/azat-io/eslint-plugin-perfectionist/releases/tag/v3.0.0). If you'd like, you can support the release with a retweet: https://x.com/azat_io_en/status/1815367279191761054

Thank you for your issue! I think this problem can be easily solved by creating custom groups.

I'll try to get on that early next week

Thank you for your issue! This bug was fixed in 8c35a7dfbe9b841f86f303c4e9fd4170b47c9c0b and released in [v3.0.0](https://github.com/azat-io/eslint-plugin-perfectionist/releases/tag/v3.0.0). If you'd like, you can support the release with a retweet: https://x.com/azat_io_en/status/1815367279191761054

Curious. An unusual problem. Thanks, I'll look into your issue.

It seems that the log retention period has expired. I tested your problem, but was unable to reproduce it. If the problem persists, I will reopen your issue.

Yes, the plugin identifies type imports as type imports, and imports where types have been imported as normal imports. ```ts // external-type group import type { Configuration } from 'webpack'...

Yep. At least that's the idea. Do you think it should work differently?

Thank you for your issue! I think this is expected behaviour. And I'll close the question. If you have a different opinion, please post.

Fixed in bd8ba3f. Released in [v3.6.0](https://github.com/azat-io/eslint-plugin-perfectionist/releases/tag/v3.6.0).