This repository was archived by the owner on Dec 2, 2023. It is now read-only.
chore(deps): update dependency prettier-plugin-organize-imports to v3 #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.4->3.2.4Release Notes
simonhaenisch/prettier-plugin-organize-imports (prettier-plugin-organize-imports)
v3.2.4: 3.2.4Compare Source
What's Changed
New Contributors
Full Changelog: simonhaenisch/prettier-plugin-organize-imports@v3.2.3...v3.2.4
v3.2.3Compare Source
v3.2.2: 3.2.2Compare Source
Fixes a performance regression introduced in
3.2.0(see #90).v3.2.1Compare Source
This version fixes the implementation of the language service host's
getCurrentDirectorymethod to return the directory containing the tsconfig, rather than usingts.sys.getCurrentDirectory(which returnsprocess.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.0Compare Source
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-typescriptpeer dependency from0.xto1.x.v3.1.1Compare Source
@volar/vue-typescriptpeer dependency to higher version which fixes removal of imports used in the template onlyv3.1.0: 3.1.0Compare Source
New Feature: Skip Destructive Code Actions
If you don't want destructive code actions (like removing unused imports), you can enable the option
organizeImportsSkipDestructiveCodeActionsvia your Prettier config.v3.0.3: 3.0.3Compare Source
Fixes a performance regression that was introduced in
3.0.2.v3.0.2: 3.0.2Compare Source
This version fixes a regression introduced by adding some file-system related methods (
fileExistsandreadFile) to the language service host (to fix #63), which revealed that the implementation ofgetScriptSnapshotwas incorrect.v3.0.1: 3.0.1Compare Source
@volar/vue-typescriptis now an optional peer dependency and requires version0.39.0or later. This should fix a couple of issues, e.g. not removing imports anymore when a component was used in the template via kebab-case.fileExistsandreadFilewhich should fix some issues withNodeNextmodule resolution.v3.0.0: 3.0.0Compare Source
Switched to a different package for Vue support, so if you're using this plugin with Vue, you'll have to install
@volar/vue-typescriptas a dev dependency now, and you can remove@vue/compiler-sfc/@vue/component-compiler-utils/vue-template-compiler.Otherwise, no breaking changes.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.