4.1.0

Bumped the peer dependency range for vue-tsc to ^2.1.0 because there was a breaking change in its API. If you're using Vue support, upgrade both packages simultaneously, e.g. npm i -D prettier-plugin-organize-imports vue-tsc.

4.0.0

Version 4.0.0 upgrades/replaces the Volar packages used for Vue support, to use the latest vue-tsc package that's part of Volar 2. To migrate, you just have to remove @volar/vue-typescript and if you're using it, also @volar/vue-language-plugin-pug, and replace it with vue-tsc and @vue/language-plugin-pug respectively. There are no breaking changes other than this.

Thanks @johnsoncodehk for contributing this 🎉

3.2.4

What's Changed

• fix: skip when formatting ranges — by @MattLish in #112

New Contributors

• @MattLish made their first contribution in #112

Full Changelog: v3.2.3...v3.2.4

3.2.3

Just readme updates to explain compatibility with Prettier 3. Also bumped TypeScript to v5 as a dev dependency to ensure compatibility.

3.2.2

Fixes a performance regression introduced in 3.2.0 (see #90).

v3.2.1

This version fixes the implementation of the language service host's getCurrentDirectory method to return the directory containing the tsconfig, rather than using ts.sys.getCurrentDirectory (which returns process.cwd()). This should prevent issues with resolving compiler plugins with Volar (which is used for Vue support).

Hopefully it doesn't break anything else 🤞 I don't think the tsconfig location is always the project root because of nested/extended tsconfigs, but it should be good enough for module resolution. If someone knows a better way of finding a project's root via the TypeScript API please let me know 🙏

v3.2.0

This version adds and fixes support for pug templates in Vue files (via @volar/vue-language-plugin-pug). Please be aware that you'll need to update your version of the @volar/vue-typescript peer dependency from 0.x to 1.x.

v3.1.1

• fix: path comparison on Windows
• fix: bump @volar/vue-typescript peer dependency to higher version which fixes removal of imports used in the template only

3.1.0

New Feature: Skip Destructive Code Actions

If you don't want destructive code actions (like removing unused imports), you can enable the option organizeImportsSkipDestructiveCodeActions via your Prettier config.

// prettierrc.js

module.exports = {
  // ...
  organizeImportsSkipDestructiveCodeActions: true,
};

3.0.3

Fixes a performance regression that was introduced in 3.0.2.