chore(deps): bump the production-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the production-dependencies group with 3 updates in the / directory: esbuild, isomorphic-dompurify and sass.

Updates esbuild from 0.20.2 to 0.23.0

Release notes

Sourced from esbuild's releases.

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:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012

... (truncated)

Changelog

Sourced from esbuild's changelog.

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)

  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:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008

... (truncated)

Commits

• 9d50680 publish 0.23.0 to npm
• ac7fd04 Revert "fix #1874: node defaults to --packages=external" (#3820)
• 626ac2c fix #3818: preserve collapsed jsx whitespace
• 7c2eb2e hashbang syntax is part of es2023
• 80c6e6e publish 0.22.0 to npm
• 196dcad fix #1874: node defaults to --packages=external
• 3f57db8 release notes for #3539
• 91663db Provide API to create a custom esbuild CLI with plugins (#3539)
• e01c0e0 also mention #3665 in release notes
• 65711b3 release notes for #3674
• Additional commits viewable in compare view

Updates isomorphic-dompurify from 2.9.0 to 2.13.0

Release notes

Sourced from isomorphic-dompurify's releases.

Updated dependencies

Changelog

• Updated dompurify and other dependencies.

See the complete changelog for more details.

Release

2.13.0

Updated dependencies

Changelog

• Updated dompurify and other dependencies.

See the complete changelog for more details.

Release

2.12.0

Updated dependencies

Changelog

• Updated dompurify.

See the complete changelog for more details.

Release

2.11.0

Updated dependencies

Changelog

• Updated dompurify.

See the complete changelog for more details.

Release

2.10.0

Commits

• 48c5996 Updated dependencies. Prepared for the release.
• ab5558e Merge pull request #274 from kkomelin/dependabot/npm_and_yarn/dompurify-3.1.6
• 791bd4f Bump dompurify from 3.1.5 to 3.1.6
• 669d181 Merge pull request #273 from kkomelin/dependabot/npm_and_yarn/ws-8.17.1
• d187119 Bump ws from 8.17.0 to 8.17.1
• 781e7d8 Merge pull request #272 from kkomelin/dependabot/npm_and_yarn/terser-5.31.1
• 955f3ef Bump terser from 5.31.0 to 5.31.1
• dafb24e Updated dependencies. Increased version.
• 4bfd3bc Merge pull request #271 from kkomelin/dependabot/npm_and_yarn/dompurify-3.1.5
• 7f4ee0a Bump dompurify from 3.1.4 to 3.1.5
• Additional commits viewable in compare view

Updates sass from 1.76.0 to 1.77.8

Release notes

Sourced from sass's releases.

Dart Sass 1.77.8

To install Sass 1.77.8, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.77.5

To install Sass 1.77.5, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Fully trim redundant selectors generated by @extend.

See the full changelog for changes in earlier releases.

Dart Sass 1.77.4

To install Sass 1.77.4, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

Embedded Sass

• Support passing Version input for fatalDeprecations as string over embedded protocol.

• Fix a bug in the JS Embedded Host where Version could be incorrectly accepted as input for silenceDeprecations and futureDeprecations in pure JS.

See the full changelog for changes in earlier releases.

Dart Sass 1.77.3

To install Sass 1.77.3, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

Dart API

... (truncated)

Changelog

Sourced from sass's changelog.

1.77.8

• No user-visible changes.

1.77.7

• Declarations that appear after nested rules are deprecated, because the semantics Sass has historically used are different from the semantics specified by CSS. In the future, Sass will adopt the standard CSS semantics.

  See the Sass website for details.

• Potentially breaking bug fix: // in certain places such as unknown at-rule values was being preserved in the CSS output, leading to potentially invalid CSS. It's now properly parsed as a silent comment and omitted from the CSS output.

1.77.6

• Fix a few cases where comments and occasionally even whitespace wasn't allowed between the end of Sass statements and the following semicolon.

1.77.5

• Fully trim redundant selectors generated by @extend.

1.77.4

Embedded Sass

• Support passing Version input for fatalDeprecations as string over embedded protocol.

• Fix a bug in the JS Embedded Host where Version could be incorrectly accepted as input for silenceDeprecations and futureDeprecations in pure JS.

1.77.3

Dart API

• Deprecation.duplicateVariableFlags has been deprecated and replaced with Deprecation.duplicateVarFlags to make it consistent with the duplicate-var-flags name used on the command line and in the JS API.

1.77.2

• Don't emit deprecation warnings for functions and mixins beginning with __.

• Allow user-defined functions whose names begin with _ and otherwise look like vendor-prefixed functions with special CSS syntax.

... (truncated)

Commits

• be9c3ac Run Windows ARM64 releases on windows-latest instead (#2275)
• d4b1939 Run pub in verbose mode on windows-arm64
• c96b5e2 Fix windows-arm64 release (#2274)
• 7203d65 Deprecated mixed declarations (#2267)
• 1edc247 Avoid [this] in Dartdoc comments (#2273)
• a164889 Enable AOT build for windows-arm64 (#2270)
• 04b6251 Parse silent comments in _interpolatedDeclarationValue() (#2266)
• 860eb5a Fix linux-ia32, linux-arm-musl, and windows-arm64 releases (#2265)
• 7aae1e6 Fix a bug where comments were incorrectly forbidden in some cases (#2264)
• cf6f9d0 Build AOT releases with native arm64 runners (#2262)
• 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

[netlify]

✅ Deploy Preview for triviaccessibility ready!

Name	Link
🔨 Latest commit	8840798
🔍 Latest deploy log	https://app.netlify.com/sites/triviaccessibility/deploys/6694b6415081e50008afb283
😎 Deploy Preview	https://deploy-preview-220--triviaccessibility.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dependabot]

Superseded by #223.