Update project dependencies

[jamesrweb]

Related Issue

N / A

PR Type

• 🐛 Bug Fix
• ✨ New Feature
• 🔨 Code Refactor
• 📝 Documentation Update
• 🧪 Test Update
• 🔧 Build/CI Update
• 🧹 Chore
• ⏪ Revert

Description

Updates the project's dependencies to their latest versions, including a major version bump of pnpm from 10.33.0 to 11.25.0. The lockfile has been regenerated accordingly and now makes use of pnpm 11's built-in supply-chain protections, removing the need for the manually maintained security overrides that previously pinned patched versions of vulnerable transitive dependencies.

Proposed Changes

• Upgrade packageManager from pnpm 10.33.0 to pnpm 11.25.0.
• Update runtime dependencies: microdiff to ^1.6.0 and react-error-boundary to ^6.1.4.
• Update dev dependencies to their latest versions, including eslint, typescript, typescript-eslint, vite (^8.2.2), vitest (^4.1.11), @vitejs/plugin-react, @testing-library/jest-dom (7.0.1), @types/node (^26.4.1), prettier and others.
• Migrate the vite-plugin-dts configuration from rollupTypes/outDir options to the new bundleTypes option (vite-plugin-dts ^5.1.0).
• Remove the manual security overrides from pnpm-workspace.yaml in favour of pnpm 11's minimumReleaseAgeStrict supply-chain setting, excluding happy-dom@20.13.2.
• Remove the now-unneeded peerDependencyRules allowed versions for @babel/eslint-parser, @babel/eslint-plugin, @vitejs/plugin-react and eslint-plugin-react-hooks.
• Add new dev dependencies: @babel/core (^8.0.1), @microsoft/api-extractor (^7.59.0) and jiti (^2.7.0).
• Regenerate pnpm-lock.yaml.

How Has This Been Tested?

• Unit Tests
• Integration Tests
• Manual Testing (please describe)

Screenshots/Recordings

Breaking Changes

• Yes (please describe)
• No

Checklist

• My code follows the code style of this project
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• My changes generate no new warnings

Additional Notes

All 43 unit tests pass (2 skipped). Vite 8.2.2 now emits a warning about configLoader: 'native' unsupported features in the Vite config (__dirname usage and extension-less imports), which can be suppressed with VITE_CONFIG_NATIVE_IGNORE_WARNING=true and addressed separately since this is something that will affect us only in the next major vite version.

[github-actions]

Coverage report for commit: 7254912
File: ./coverage/clover.xml

Cover ┌─────────────────────────┐ Freq.
   0% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  10% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  20% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  30% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  40% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  50% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  60% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  70% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  80% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  90% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
 100% │ ███████████████████████ │ 100.0%
      └─────────────────────────┘
 *Legend:* █ = Current Distribution 

Summary - Lines: 100.00% | Methods: 100.00% | Branches: 96.67%

Files	Lines	Methods	Branches
src/components
P5Canvas.tsx	100.00%	100.00%	100.00%
P5CanvasGuard.tsx	100.00%	100.00%	87.50%
P5CanvasWithSketch.tsx	100.00%	100.00%	100.00%
src/constants
CanvasContainerClassName.ts	100.00%	100.00%	100.00%
src/contracts
CanvasContainer.ts	100.00%	100.00%	100.00%
CanvasContainerRef.ts	100.00%	100.00%	100.00%
P5CanvasInstance.ts	100.00%	100.00%	100.00%
P5CanvasInstanceRef.ts	100.00%	100.00%	100.00%
P5CanvasInternalProps.ts	100.00%	100.00%	100.00%
P5CanvasProps.ts	100.00%	100.00%	100.00%
Sketch.ts	100.00%	100.00%	100.00%
SketchProps.ts	100.00%	100.00%	100.00%
Updater.ts	100.00%	100.00%	100.00%
p5.ts	100.00%	100.00%	100.00%
src
main.tsx	100.00%	100.00%	100.00%
src/utils
createP5CanvasInstance.ts	100.00%	100.00%	100.00%
logErrorBoundaryError.ts	100.00%	100.00%	100.00%
propsAreEqual.ts	100.00%	100.00%	100.00%
removeP5CanvasInstance.ts	100.00%	100.00%	100.00%
updateP5CanvasInstance.ts	100.00%	100.00%	100.00%

_{🤖 comment via lucassabreu/comment-coverage-clover}

[yevdyko]

Let's go 🚀 Thanks!