search

neoki07 / prettier-plugin-astro-organize-imports

A Prettier plugin for formatting imports in Astro files
https://www.npmjs.com/package/prettier-plugin-astro-organize-imports
MIT License
37 stars 2 forks source link

chore(deps): bump the dependencies group across 1 directory with 8 updates #184

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the dependencies group with 8 updates in the / directory:

Package From To
@astrojs/compiler 2.9.2 2.10.3
@changesets/cli 2.27.7 2.27.8
@types/node 22.0.0 22.7.0
esbuild 0.23.0 0.24.0
lefthook 1.7.9 1.7.16
prettier-plugin-organize-imports 4.0.0 4.1.0
prettier-plugin-tailwindcss 0.6.5 0.6.8
vitest 2.0.4 2.1.1

Updates @astrojs/compiler from 2.9.2 to 2.10.3

Release notes

Sourced from @​astrojs/compiler's releases.

@​astrojs/compiler@​2.10.3

Patch Changes

  • 5d0023d: Fixes sourcemapping for CRLF line endings wrongfully including the last character
  • f55a2af: Resolves an issue where the class:list directive was not correctly merging with the class attribute.

@​astrojs/compiler@​2.10.2

Patch Changes

  • f05a7cc: Adjust TSX output to return ranges using UTF-16 code units, as it would in JavaScript

@​astrojs/compiler@​2.10.1

Patch Changes

  • 21b7b95: Revert the transformation of top-level returns into throws in TSX as it was buggy in numerous situations
  • af471f5: Fixes positions for extracted tags being wrong when using IncludeStyles and IncludeScripts set to false

@​astrojs/compiler@​2.10.0

Minor Changes

  • 1d684b1: Adds detected language to extracted style tags in TSX

Patch Changes

  • 7fa6577: Transform top level returns into throws in the TSX output
Commits


Updates @changesets/cli from 2.27.7 to 2.27.8

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.27.8

Patch Changes

Commits


Updates @types/node from 22.0.0 to 22.7.0

Commits


Updates esbuild from 0.23.0 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "fs";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

... (truncated)

Commits


Updates lefthook from 1.7.9 to 1.7.16

Release notes

Sourced from lefthook's releases.

v1.7.16

Changelog

  • eb24c87bc72f72a2dd1b614a5685094bd1d63d20 chore: enhance some code parts (#824)
  • 3daab42c2fd0334e3134672d741c63068cc122dd fix: quote script path (#823)

v1.7.15

Changelog

  • 2df5428fbf9bc550c2b6695e940d2a004e7ea30b deps: August 2024 (#802)
  • 72de5de90dbc0243430e7278b4f5b8dfaa94f429 fix: add better colors control (#812)

v1.7.14

Changelog

v1.7.13

Changelog

  • 1aa06dc0801bc54bbc410ba6234a7b37fb13b144 feat: support openbsd (#808)

v1.7.12

Changelog

  • 26bf489c503ae42b7eea75add8e2bd73d134b2c4 fix: log stderr in debug logs only (#804)

v1.7.11

Changelog

  • 5c336d81a5bdfb4b527d6cea9859a38af20d306a fix: revert packaging change (#796)

v1.7.10

Changelog

  • b32fd3351664e8e4dd4da231f0e1c360ca0d549f deps: July 2024 (#795)
  • 19b7a7290ed17bdb4b2cf7ffdbd8c8ba3c36b692 packaging(npm): try direct reference for lefthook executable (#794)
Changelog

Sourced from lefthook's changelog.

1.7.16 (2024-09-23)

1.7.15 (2024-09-02)

1.7.14 (2024-08-17)

Fix lefthook NPM package to include OpenBSD package as optional dependency.

1.7.13 (2024-08-16)

1.7.12 (2024-08-09)

1.7.11 (2024-07-29)

1.7.10 (2024-07-29)

Commits


Updates prettier-plugin-organize-imports from 4.0.0 to 4.1.0

Release notes

Sourced from prettier-plugin-organize-imports's releases.

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.

Changelog

Sourced from prettier-plugin-organize-imports's changelog.

Version 4.1.0 bumps 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.

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.

Version 3.2.4 implements a fix to skip when formatting ranges (i.e. if the plugin is requested to format a range, it doesn't do anything because it would lack the full file context).

Version 3.2.3 updates the readme with instructions for Prettier 3.

Version 3.2.2 fixes a performance regression introduced in 3.2.0.

Version 3.2.1 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).

Version 3.2.0 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.

Version 3.1.0 adds an option to skip destructive code actions like removing unused imports.

Version 3.0.3 fixes a performance regression introduced in 3.0.2.

Version 3.0.2 fixes a regression introduced by adding some file-system related methods to the language service host (to fix a bug), which revealed that another method's implementation was incorrect.

Version 3.0.1 bumps the @volar/vue-typescript version to fix more edge cases, e. g. not removing imports when a component is used via kebab-case naming. @volar/vue-typescript is now defined as an optional peer dependency and you'll need to install version 0.39 or later. Furthermore a fix has been added that should help support more module resolution algorithms.

Version 3.0.0 switches to a different package for Vue support, which fixes some more issues, e. g. support for setup scripts. No breaking changes otherwise.

Version 2.3.4 fixes an issue with Vue v2 files.

Version 2.3.3 fixes a bug where default imports were removed erroneously.

Version 2.3.1 adds debug logs and fixes Vue.js support.

Version 2.2.0 adds a compiler options cache to improve performance.

Version 2.1.0 adds support for Vue.js (.vue files).

Version 2.0.0 adds support for the parsers babel (i. e. JavaScript) and babel-ts which are only available since Prettier v2 (and thus the peer dependency has received a major bump).

Commits
  • b7c15ad 4.1.0
  • 2e9c480 chore: update dev dependencies
  • fb7e872 docs: update changelog
  • 3fb452e feat: support vue-tsc v2.1 (#136)
  • 4678129 chore(ci): run on node 22
  • fa99724 chore(ci): fix run-script invocation
  • 3ea4a81 chore: use tsc to type-check the project
  • 59c5329 chore(tests): upgrade ava from v3 to v6
  • b253038 fix: drop @vue/language-plugin-pug as peer dependency
  • See full diff in compare view


Updates prettier-plugin-tailwindcss from 0.6.5 to 0.6.8

Release notes

Sourced from prettier-plugin-tailwindcss's releases.

v0.6.8

v0.6.7

  • Improved performance with large Svelte, Liquid, and Angular files (#312)
  • Add support for @plugin and @config in v4 (#316)
  • Add support for Tailwind CSS v4.0.0-alpha.25 (#317)

v0.6.6

  • Add support for prettier-plugin-multiline-arrays (#299)
  • Add resolution cache for known plugins (#301)
  • Support Tailwind CSS v4.0.0-alpha.19 (#310)
Changelog

Sourced from prettier-plugin-tailwindcss's changelog.

[0.6.8] - 2024-09-24

[0.6.7] - 2024-09-24

  • Improved performance with large Svelte, Liquid, and Angular files (#312)
  • Add support for @plugin and @config in v4 (#316)
  • Add support for Tailwind CSS v4.0.0-alpha.25 (#317)

[0.6.6] - 2024-08-09

  • Add support for prettier-plugin-multiline-arrays (#299)
  • Add resolution cache for known plugins (#301)
  • Support Tailwind CSS v4.0.0-alpha.19 (#310)
Commits


Updates vitest from 2.0.4 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()


const [firstPost] = screen.getByRole('listitem').all()


await firstPost.getByRole('button', { name: 'Delete' }).click()


expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
  • 16aa76c fix(browser): make example test callbacks async (#6484)
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
  • b2be23e chore: release v2.1.0-beta.7
  • 0b44722 fix: ignore importer when resolving Vitest (#6469)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions