Skip to content

Bump wp-env & wp-scripts and split test environment (:8889)#15

Merged
mcsf merged 3 commits into
mainfrom
update/wp-scripts-32-wp-env-11
Apr 23, 2026
Merged

Bump wp-env & wp-scripts and split test environment (:8889)#15
mcsf merged 3 commits into
mainfrom
update/wp-scripts-32-wp-env-11

Conversation

@mcsf

@mcsf mcsf commented Apr 23, 2026

Copy link
Copy Markdown
Member

Summary

  • Bump @wordpress/env to v11:
    • Playground runtime fixes
    • Better UI
    • --auto-port support
  • Bump @wordpress/scripts to v32 to match (first version whose peer dep accepts @wordpress/env >=10):
    • Upgrades ESLint from v8 to v10 and switches to flat config by default
  • Split dev and test environments into .wp-env.json (port 8888) and .wp-env.test.json (port 8889), following wp-env's deprecation of testsEnvironment etc.
    • Add npm run test:env:start
    • Point Playwright's fallback URL at the test port.
  • Fix ESLint issues revealed by the ESLint upgrade, including missing @wordpress/ dependencies.

Test plan

  • npm run env:start starts on port 8888
  • npm run test:env:start starts on port 8889
  • npm run test:e2e succeeds after testing against :8889
  • npm run lint:js and npm run build succeed

mcsf added 3 commits April 23, 2026 12:41
Lots of goodness in wp-env v11, including Playground runtime fixes,
better "UI", and `--auto-port`, which could come in handy.

As for wp-scripts, is the first version whose peer dependency accepts
@wordpress/env >=10 (v30 requires ^10).
Split dev env (8888) and test env (8889) into separate files
(.wp-env.json and .wp-env.test.json), in agreement with the wp-env and
its deprecation of testsEnvironment, etc.

Point Playwright's fallback URL at the test port accordingly.
@mcsf mcsf changed the title Bump wp-scripts to v32 and wp-env to v11; split test environment Bump wp-env & wp-scripts and split test environment (:8889) Apr 23, 2026
@mcsf mcsf merged commit 32cf6bb into main Apr 23, 2026
6 checks passed
@mcsf mcsf deleted the update/wp-scripts-32-wp-env-11 branch April 23, 2026 12:59
priethor added a commit that referenced this pull request May 1, 2026
Renumbered the DataViews column-interaction tech-debt entry to #15 so it
sits after main's new system-field entries (#12-14), and updated the
tech-debt.md cross-references in DataViewColumnInteractions.js and
index.scss to match.
priethor added a commit that referenced this pull request May 1, 2026
Four new entries:

- #15 DataViews has no public per-column menu-item slot. PR D takes
  over the header by hiding the built-in trigger; upstream a
  field.menuItems extension surface so consumers don't have to fork.
- #16 Synthetic ghost column is pinned in view.fields. If
  enableHiding handling shifts upstream, fork the field list.
- #17 Field schema actions are table-layout only. A future Manage
  fields modal/panel covers grid/list.
- #18 Select / multi-select fields are created without inline option
  editing. The route still accepts options; the UI doesn't surface it
  yet. A future field-edit dialog will.
@priethor priethor added this to the 0.1.0 milestone May 28, 2026
@priethor priethor added the type: tooling CI, release, packaging, scripts, and repo automation. label May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: tooling CI, release, packaging, scripts, and repo automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants