chore: Update deps

[larseggert]

There are these yarn messages, which I don't understand, but @NGPixel may.

➤ YN0000: ┌ Resolution step
➤ YN0060: │ @parcel/optimizer-image@npm:2.6.2 provides @parcel/core (pec760) with version 2.5.0, which doesn't satisfy what @parcel/workers requests
➤ YN0060: │ @parcel/types@npm:2.6.2 provides @parcel/core (p1835f) with version 2.5.0, which doesn't satisfy what @parcel/fs requests
➤ YN0060: │ @parcel/types@npm:2.6.2 provides @parcel/core (p40766) with version 2.5.0, which doesn't satisfy what @parcel/workers requests
➤ YN0060: │ @parcel/types@npm:2.6.2 provides @parcel/core (p60182) with version 2.5.0, which doesn't satisfy what @parcel/cache requests
➤ YN0060: │ @parcel/types@npm:2.6.2 provides @parcel/core (pe24cb) with version 2.5.0, which doesn't satisfy what @parcel/package-manager requests
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed

[NGPixel]

These warnings are because these parcel packages don't properly specify their dependencies and rely on some other package including them (which is bad practice, see this blog post).

The solution is to specify them in .yarnrc.yml (see https://github.com/ietf-tools/datatracker/blob/main/.yarnrc.yml#L7-L22)

So for example, in your warnings, the first one being "@parcel/workers" missing dependency "@parcel/core", you would add to .yarnrc.yml:

"@parcel/workers@*":
  dependencies:
    "@parcel/core": "*"

These warnings should then disappear the next time you run yarn.

[larseggert]

I added that to .yarnrc.yml, but the warning still shows when I do yarn rebuild.

I also noticed there are already similar blocks for @parcel/optimizer-image and @parcel/types, but they don't suppress the warnings either?

[NGPixel]

It works using this .yarnrc.yml:

defaultSemverRangePrefix: ""

enableTelemetry: false

nodeLinker: pnp

packageExtensions:
  "@parcel/optimizer-image@*":
    dependencies:
      "@parcel/core": "2.6.2"
  "@parcel/fs@*":
    dependencies:
      "@parcel/core": "2.6.2"
  "@parcel/workers@*":
    dependencies:
      "@parcel/core": "2.6.2"
  "@parcel/cache@*":
    dependencies:
      "@parcel/core": "2.6.2"
  "@parcel/package-manager@*":
    dependencies:
      "@parcel/core": "2.6.2"
  "select2-bootstrap-5-theme@*":
    dependencies:
      "@popperjs/core": "*"

plugins:
  - path: .yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs
    spec: "@yarnpkg/plugin-interactive-tools"

supportedArchitectures:
  cpu:
    - "x64"
    - "arm64"
  os:
    - "darwin"
    - "linux"
    - "win32"

yarnPath: .yarn/releases/yarn-3.2.0.cjs

[rjsparks]

I made a mistake merging this - too trained to ignore the test runs. I'm going to revert it. Please bring in a new PR where the Agenda_js tests don't fail

[larseggert]

@rjsparks see #4203