fix: remove workspaces field from package.json and update uuid to v14

[fabiankaegy]

Description of the Change

Fixes #408.

The published npm package shipped "workspaces": ["example/"] in its package.json. While the example/ directory itself was already excluded from the tarball by the files allowlist, the workspaces field persisted in the published package.json, making npm treat the installed package as workspace-aware during dependency resolution in consuming projects — which breaks npm overrides for any transitive dependency of this package.

Changes

• Remove the workspaces field from package.json (the actual fix from the issue).
• Rewire the test-env scripts: example/ is now a standalone npm project. build-test-env builds the root package, runs npm install --prefix example, then builds the example plugin; start-test-env uses --prefix example instead of -w example/. This keeps the e2e CI workflow working, since root npm ci no longer installs example's dependencies.
• Add jest-environment-jsdom as an explicit devDependency — regression fix uncovered while testing: it was previously only available through workspace hoisting from example's @wordpress/scripts tree, so removing workspaces silently broke npm test (10up-toolkit hardcodes testEnvironment: 'jsdom').
• Update uuid from ^9.0.1 to ^14.0.1 so consumers get a current uuid without resorting to overrides at all. Dropped @types/uuid (uuid ships its own types since v7). Both usage sites (content-picker, repeater) use the unchanged v4 named export — no code changes needed.
• Add jest-unit.config.js (10up-toolkit's project-root override mechanism) widening transformIgnorePatterns so Jest transforms uuid's ESM-only build. uuid v13+ ships no CommonJS export condition; webpack-based consumer builds handle this transparently (verified below), but Jest needs the transform.
• Regenerate lockfiles: root package-lock.json loses the example workspace tree (verified semantically: 0 unexpected additions or version changes besides uuid and the jest-environment-jsdom tree); example/package-lock.json is newly committed for the now-standalone example project.
• Update CONTRIBUTING.md for the new two-project setup.

CI fixes (follow-up commits)

• Regenerate the lockfile with npm 10 (matching .nvmrc's node 20 used by CI): npm 10's resolver requires a nested stylelint@16 subtree under @wordpress/ui that npm 11 prunes, so the initially npm 11-written lockfile failed npm ci on the runners. Additions only, no version changes; validated with npm ci --dry-run under both npm 10 and npm 11.
• Pin the publish workflow's npm upgrade to npm@11: npm@12 requires node >= 22, so npm install -g npm@latest now fails on the node 20 runners — this release_testing breakage predates this PR and hits every PR.

Known unrelated failure

The Cypress e2e job fails with Cannot destructure property 'documentElement' of 'z' as it is null in every spec — the identical failure exists on develop (first seen in the July 16 run of the 1.22.3 release commit, a version-bump-only change), so it's pre-existing environment drift (likely wp-env pulling a newer WordPress), not caused by this PR. The rewired build-test-env/start-test-env scripts themselves work: the CI run builds the example plugin, boots the environment, and executes all 35 tests.

How to test the Change

1. npm ci && npm test && npm run build — unit tests and build pass.
2. npm run build-test-env — full clean pipeline (root build → example install → example webpack build) succeeds, confirming a webpack consumer bundles ESM-only uuid@14 through the CJS dist output.
3. Repro from the issue: npm pack, then in a fresh project add the tarball as a dependency with "overrides": { "uuid": "^14.0.0" } and run npm install && npm ls uuid. The extracted tarball's package.json has no workspaces field, and npm ls uuid shows a single deduped uuid@14.0.1 — no nested stale copy. (With this change, no override is needed in the first place.)

Changelog Entry

Fixed - remove workspaces field from the published package.json, which broke npm overrides for transitive dependencies in consuming projects
Changed - update uuid dependency from v9 to v14

Credits

Props @mattradford-sage (issue report and suggested fix), @fabiankaegy

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change where applicable.
• All new and existing tests pass.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes an npm packaging issue where the published package.json included a workspaces field (breaking npm overrides in consuming projects), and updates the uuid dependency to a newer major version while keeping local e2e workflows working without npm workspaces.

Changes:

• Removed "workspaces" from the published package.json and rewired test-env scripts to use a standalone example/ project.
• Updated uuid to ^14.0.1, removed @types/uuid, and added jest-environment-jsdom as an explicit devDependency.
• Added jest-unit.config.js to ensure Jest transforms uuid (ESM) under node_modules, and updated CONTRIBUTING.md to reflect the new setup.

Reviewed changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated 3 comments.

File	Description
package.json	Removes workspace config, updates dependencies, and updates env scripts to run against the standalone example/ project.
jest-unit.config.js	Extends 10up-toolkit Jest config to transform uuid (ESM) instead of ignoring it under node_modules.
CONTRIBUTING.md	Updates contributor workflow docs for separate root + example/ installs/builds.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cypress]

10up Block Components    Run #1077

Run Properties:   Failed #1077  •  7047228532: fix: pin publish workflow npm upgrade to npm@11

Project	10up Block Components
Branch Review	fix/remove-workspaces-from-published-package
Run status	Failed #1077
Run duration	02m 13s
Commit	7047228532: fix: pin publish workflow npm upgrade to npm@11
Committer	Fabian Kägy
View all properties for this run ↗︎

---

Test results
Failures	12
Flaky	0
Pending	0
Skipped	23
Passing	0
View all changes introduced in this branch ↗︎

---

Tests for review

  ColorSettings.spec.js • 1 failed test

View Output

Test		Artifacts
ColorSettings > Allows the user to pick the block and displays it		Test Replay Screenshots

  Counter.spec.js • 1 failed test

View Output

Test		Artifacts
Counter > Allows the user to pick the block and displays it		Test Replay Screenshots

  IconPicker.spec.js • 1 failed test

View Output

Test		Artifacts
IconPicker > allows the user to use the post picker to change an icon and displays it		Test Replay Screenshots

  Image.spec.js • 1 failed test

View Output

Test		Artifacts
Image > allows the user to pick an image from the media library and displays it inline		Test Replay Screenshots

  Link.spec.js • 1 failed test

View Output

Test		Artifacts
Link > allows the editor to pick a link directly inline		Test Replay Screenshots

The first 5 failed specs are shown, see all 11 specs in Cypress Cloud.

[github-actions]

🎉 A new testing version of this package has been published to NPM. You can install it with npm install @10up/block-components@testing-410