ci(js-dev): bump the development-dependencies group across 1 directory with 6 updates

[dependabot]

Bumps the development-dependencies group with 6 updates in the / directory:

Package	From	To
@tailwindcss/typography	0.5.13	0.5.14
autoprefixer	10.4.19	10.4.20
esbuild	0.21.3	0.23.1
postcss	8.4.38	8.4.41
prettier-plugin-tailwindcss	0.5.14	0.6.6
tailwindcss	3.4.3	3.4.10

Updates @tailwindcss/typography from 0.5.13 to 0.5.14

Release notes

Sourced from @​tailwindcss/typography's releases.

v0.5.14

• Fix table text alignment (#346)

Changelog

Sourced from @​tailwindcss/typography's changelog.

[0.5.14] - 2024-08-07

• Fix table text alignment (#346)

Commits

• 7b43b3b 0.5.14
• 41b694d Update changelog
• 815dfc4 Fix table text align (#346)
• 2745585 Bump braces and jest (#353)
• f364a16 use Node 22 in CI workflows (#354)
• See full diff in compare view

Updates autoprefixer from 10.4.19 to 10.4.20

Release notes

Sourced from autoprefixer's releases.

10.4.20

• Fixed fit-content prefix for Firefox.

Changelog

Sourced from autoprefixer's changelog.

10.4.20

• Fixed fit-content prefix for Firefox.

Commits

• dae6eb4 Release 10.4.20 version
• ee43652 Fix fit-content for Firefox
• cf80824 Update dependencies
• 49d5ec6 Move to pnpm 9
• See full diff in compare view

Updates esbuild from 0.21.3 to 0.23.1

Release notes

Sourced from esbuild's releases.

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";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

v0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

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
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

... (truncated)

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• 9d50680 publish 0.23.0 to npm
• Additional commits viewable in compare view

Updates postcss from 8.4.38 to 8.4.41

Release notes

Sourced from postcss's releases.

8.4.41

• Fixed types (by @​nex3 and @​querkmachine).
• Cleaned up RegExps (by @​bluwy).

8.4.40

• Moved to getter/setter in nodes types to help Sass team (by @​nex3).

8.4.39

• Fixed CssSyntaxError types (by @​romainmenke).

Changelog

Sourced from postcss's changelog.

8.4.41

• Fixed types (by @​nex3 and @​querkmachine).
• Cleaned up RegExps (by @​bluwy).

8.4.40

• Moved to getter/setter in nodes types to help Sass team (by @​nex3).

8.4.39

• Fixed CssSyntaxError types (by @​romainmenke).

Commits

• 57e0211 Release 8.4.41 version
• f27134f Update dependencies
• 146d31c Merge pull request #1952 from nex3/rule-props
• 3707c3b Merge remote-tracking branch 'origin/main' into rule-props
• 9ab3619 Declare Input.toJSON()
• be59ad4 Remove dead website
• 165154b Update dependencies
• 6127a44 Declaration#variable do not have setter
• 536726d Fix type
• 58fa0ef Sort keys
• Additional commits viewable in compare view

Updates prettier-plugin-tailwindcss from 0.5.14 to 0.6.6

Release notes

Sourced from prettier-plugin-tailwindcss's releases.

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)

v0.6.5

• Only re-apply string escaping when necessary (#295)

v0.6.4

• Export PluginOptions type (#292)

v0.6.3

• Improve detection of string concatenation (#288)

v0.6.2

Changed

• Only remove duplicate Tailwind classes (#277)
• Make sure escapes in classes are preserved in string literals (#286)

v0.6.1

Added

• Add new tailwindPreserveDuplicates option to disable removal of duplicate classes (#276)

Fixed

• Improve handling of whitespace removal when concatenating strings (#276)
• Fix a bug where Angular expressions may produce invalid code after sorting (#276)
• Disabled whitespace and duplicate class removal for Liquid and Svelte (#276)

v0.6.0

Changed

• Remove duplicate classes (#272)
• Remove extra whitespace around classes (#272)

Changelog

Sourced from prettier-plugin-tailwindcss's changelog.

[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)

[0.6.5] - 2024-06-17

• Only re-apply string escaping when necessary (#295)

[0.6.4] - 2024-06-12

• Export PluginOptions type (#292)

[0.6.3] - 2024-06-11

• Improve detection of string concatenation (#288)

[0.6.2] - 2024-06-07

Changed

• Only remove duplicate Tailwind classes (#277)
• Make sure escapes in classes are preserved in string literals (#286)

[0.6.1] - 2024-05-31

Added

• Add new tailwindPreserveDuplicates option to disable removal of duplicate classes (#276)

Fixed

• Improve handling of whitespace removal when concatenating strings (#276)
• Fix a bug where Angular expressions may produce invalid code after sorting (#276)
• Disabled whitespace and duplicate class removal for Liquid and Svelte (#276)

[0.6.0] - 2024-05-30

Changed

• Remove duplicate classes (#272)
• Remove extra whitespace around classes (#272)

Commits

• 0368ffb 0.6.6
• b7830c6 Support Tailwind CSS v4.0.0-alpha.19 (#310)
• ee50b9b Add cache for known plugins (#301)
• f69f739 Remove versions key in tests
• f6661cd Fix code style
• c0c5040 Convert tests to typescript
• b2c8574 Fix type error
• 96d9d18 Hide Pug debug logs during testing
• c5eed72 Add compatibility with prettier-plugin-multiline-arrays (#299)
• f101793 Move fixtures' expected outputs to the fixture directories (#298)
• Additional commits viewable in compare view

Updates tailwindcss from 3.4.3 to 3.4.10

Release notes

Sourced from tailwindcss's releases.

v3.4.10

Fixed

• Bump versions of plugins in the Standalone CLI (#14185)

v3.4.9

Fixed

• No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Fixed

• Fix minification when using nested CSS (#14105)
• Warn when broad glob patterns are used in the content configuration (#14140)

v3.4.7

Fixed

• Fix class detection in Slim templates with attached attributes and ID (#14019)
• Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14037)

v3.4.6

Fixed

• Fix detection of some utilities in Slim/Pug templates (#14006)

Changed

• Loosen :is() wrapping rules when using an important selector (#13900)

v3.4.5

Fixed

• Disable automatic var() injection for anchor properties (#13826)
• Use no value instead of blur(0px) for backdrop-blur-none and blur-none utilities (#13830)
• Add .mts and .cts config file detection (#13940)
• Don't generate utilities like px-1 unnecessarily when using utilities like px-1.5 (#13959)
• Always generate -webkit-backdrop-filter for backdrop-* utilities (#13997)

v3.4.4

Fixed

• Make it possible to use multiple <alpha-value> placeholders in a single color definition (#13740)
• Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#13770)
• Support negative values for {col,row}-{start,end} utilities (#13781)
• Update embedded browserslist database (#13792)

Changelog

Sourced from tailwindcss's changelog.

[3.4.10] - 2024-08-13

Fixed

• Bump versions of plugins in the Standalone CLI (#14185)

[3.4.9] - 2024-08-08

Fixed

• No longer warns when broad glob patterns are detecting vendor folders

[3.4.8] - 2024-08-07

Fixed

• Fix minification when using nested CSS (#14105)
• Warn when broad glob patterns are used in the content configuration (#14140)

[3.4.7] - 2024-07-25

Fixed

• Fix class detection in Slim templates with attached attributes and ID (#14019)
• Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14037)

[3.4.6] - 2024-07-16

Fixed

• Fix detection of some utilities in Slim/Pug templates (#14006)

Changed

• Loosen :is() wrapping rules when using an important selector (#13900)

[3.4.5] - 2024-07-15

Fixed

• Disable automatic var() injection for anchor properties (#13826)
• Use no value instead of blur(0px) for backdrop-blur-none and blur-none utilities (#13830)
• Add .mts and .cts config file detection (#13940)
• Don't generate utilities like px-1 unnecessarily when using utilities like px-1.5 (#13959)
• Always generate -webkit-backdrop-filter for backdrop-* utilities (#13997)

[3.4.4] - 2024-06-05

Fixed

... (truncated)

Commits

• f07dbff 3.4.10
• c4f2362 Bump versions of plugins in the Standalone CLI (#14185)
• f65023e 3.4.9
• 702ba6a Don't warn about broad globs in vendor folders (#14147)
• 1676118 3.4.8
• 69c81f2 rename master to main
• 858696a Warn when broad glob patterns are used in the content configuration (#14140)
• 1f23c2e Bump to latest cssnano v6 (#14105)
• 28bd90e Automate checksum generation for standalone CLI (#14081)
• 9824cb6 Update version in package.json
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions