Update/Audit NPM Dependencies for 6.9

[desrosj]

Previously:

• #62220 (6.8)
• #62137 (6.7)
• #61498 (6.6)
• #59658 (6.5)
• #58863 (6.4)
• #57657 (6.3)
• #57535 (6.2)
• #56641 (6.1)
• #54727 (6.0)
• #53361 (5.9)
• #52624 (5.8)
• #51801 (5.7)
• #50769 (5.6)
• #49768 (5.5)
• #49547 (5.4)
• #48203 (5.3)
• #46039 (5.1)
• #45064 (5.0)
• #38199 (4.7)
• #36520 (4.6)
• #35104 (4.5)
• #34177 (4.4)
• #31700 (4.3)
• #31489 (4.2)
• #30141 (4.1)
• #27340 (4.0)
• #26073 (3.9)

Trac Ticket: Core-63171

[desrosj]

In 60348:

Build/Test Tools: Commit changes to built theme files for PRs.

When there are uncommitted changes to versioned files in default themes, the theme testing workflow will now store the patch file required for the changes to be committed back to the pull request.

See #63170, #63171.

[desrosj]

In 60349:

Build/Test Tools: Create groups for bundled theme Dependabot PRs.

Follow up to [60347].

See #63170, #63171.

[desrosj]

In 60350:

Build/Test Tools: Only check for changes to versioned files once.

Because the theme testing workflow now stores a patch file with changes to versioned files, there is no need for the separate workflow to run and do the same when only theme files are updated.

Follow up to [60348].

See #63170, #63171.

e2e-test-utils was replaced with e2e-test-utils-playwright in https://core.trac.wordpress.org/ticket/59517 and is no longer needed. This removes a few dependencies but we can't get rid of Puppeteer just yet because grunt-contrib-qunit still depends on it for the QUnit tests.

[johnbillion]

In 60429:

Build/Test Tools: Remove the e2e-test-utils package which is no longer used.

This package was superseded by e2e-test-utils-playwright in #59517.

See #63171

Committed in https://core.trac.wordpress.org/changeset/60429

[jorbin]

In 61011:

Build/Test Tools: Update caniuse data.

Browsers data (caniuse-lite) is 9 months old, so make it more up to date before beta 1.

See #63171.

Trac ticket: Core-63171

This updates all npm dependencies for default themes except the following in Twenty Twenty-One:

• sass: Updating this results in duplicate class declarations with just inline comment blocks.
• stylelint-related packages - causing unexpected changes to file indentation.
• eslint is only updated to the highest 8.x version (9.x is not yet supported by WordPress-related packages, see ​https://github.com/WordPress/gutenberg/pull/65648).

Trac ticket: Core-63171.

[desrosj]

In 61205:

Build/Test Tools: Update devDependencies.

This updates the following devDependencies:

• @playwright/test from 1.50.1 to 1.56.1.
• @pmmmwh/react-refresh-webpack-plugin from 0.5.15 to 0.6.1.
• autoprefixer from 10.4.20 to 10.4.22.
• chalk from 5.4.1 to 5.6.2.
• copy-webpack-plugin from 13.0.0 to 13.0.1.
• cssnano from 7.0.6 to 7.1.2.
• dotenv from 16.4.7 to 17.2.3.
• dotenv-expand from 12.0.1 to 12.0.3.
• grunt-sass from 4.0.0 to 4.0.1.
• postcss from 8.5.3 to 8.5.6.
• qunit from 2.23.1 to 2.24.2.
• sass from 1.85.1 to 1.94.0.
• terser-webpack-plugin from 5.3.12 to 5.3.14.
• uuid from 11.1.0 to 13.0.0.
• wait-on from 8.0.2 to 9.0.3.

A new variable, DOTENV_CONFIG_QUIET, has been added to the .env.example file to silence tips output by the dotenv dependency.

Additionally, npm audit fix has been run.

Props peterwilsoncc, desrosj.
See #63171.

Merged in https://core.trac.wordpress.org/changeset/61205.

The browserlist config in TT2 and TT5 are using older versions than the other themes. It would be good if they were consistent

I think I'd like to look at that separately. Historically, I believe that we have not changed the browser support policies for default themes to avoid possibly breaking child themes or custom CSS.

Hat tip to @peterwilsoncc, I just realized that TT2 and TT5 now have package.json files. I've gone and updated the dependencies for those themes as well.

[desrosj]

In 61206:

Build/Test Tools: Update dependencies for bundled themes.

This updates the devDependencies for each of the default themes with package.json files with a few exceptions:

• eslint: This was updated to the latest 8.x version only since 9.x is not yet properly supported by @wordpress/eslint-plugin.
• stylelint-related packages: these updates are resulting in formatting changes. These need to be examined more carefully as they’re likely undesired and require adjustments to the configuration file.

Props peterwilsoncc, desrosj.
Fixes #63171.

[desrosj]

I've created #64230 for the 7.0 release cycle.