Skip to content

Add Lerna - #184

Merged
adamziel merged 5 commits into
trunkfrom
add-lerna
Apr 1, 2023
Merged

adamziel merged 5 commits into
trunkfrom
add-lerna

Conversation

@adamziel

@adamziel adamziel commented Apr 1, 2023

Copy link
Copy Markdown
Collaborator

Description

It's hard to publish all the npm packages living in this repo without a tool. After considering changesets and Lerna I decided to go with the latter since it's maintained by the authors of nx – another tool used in this project.

Solves #148

Comment thread README.md
@@ -1,4 +1,4 @@
# WordPress Playground
# WordPress Playground and PHP WASM (WebAssembly)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already a in trunk, I must have squashed this PR to the last trunk commit. It doesn't matter, I'll leave it like this.

adamziel added 4 commits April 1, 2023 16:49
This is useful in itself and makes the client package self-contained. In
this instance we need it to avoid producing an invalid list of
dependencies in the final package.json. This package technically depends
on php-wasm/web, but takes great care not to import anything from it
other than TypeScript types that are then released in a rollup file.
@adamziel
adamziel merged commit ad7afe9 into trunk Apr 1, 2023
@adamziel
adamziel deleted the add-lerna branch April 1, 2023 15:01
@adamziel adamziel mentioned this pull request Apr 1, 2023
akirk added a commit that referenced this pull request Sep 3, 2026
Chrome 150 deprecated `navigator.modelContext` in favour of
`document.modelContext` (webmachinelearning CG issue 173, PR #184) but
still serves it. Playground provides the registry itself, so a plugin
that has not migrated — the Abilities-to-WebMCP bridges register through
`navigator` with no fallback — worked in Chrome and threw only here.

Both registries now expose the deprecated global as a getter returning
the same instance, warning once on first access the way a platform
deprecation does. `document.modelContext` stays the documented surface,
and this goes when Chrome removes it.

The test registers its runtime-added tool through the alias, so the
proxy path is covered from the deprecated global too.

Claude-Session: https://claude.ai/code/session_01SES9wgwFmrkkhwqfmfMuMU
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant