Under the hood
Useful1 Signal1
Every schema in the bundle moved to standalone builder functions to cut size.
What's wrong with this entry?
Anonymous. No account, no email.
What
Every schema in the bundle, covering tool inputs and outputs, plugin manifests, settings, memory and artifacts, was rewritten from the namespaced schema builders to standalone functions. Field names, descriptions and validation behave the same; this is a bundle-size change.
Details
- The previous build has 1486 uses of the namespaced string builder and 569 of the namespaced object builder; this build has none of either, with roughly 963 direct object builder call sites.
- Example: a hook type that was a namespaced literal with the description "MCP tool hook type" is now a bare literal call, and its server field a bare string call described as the name of an already-configured MCP server to invoke.
- The error instance check switched to the corresponding direct class. Several hunks in this group are only the resulting reformatting.
Evidence
w.object(, MCP tool hook type
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Bulk identifier renames from the bundler
Both mention build
-
v2.1.232
Version 2.1.232
Both mention build
-
v2.1.220
Bundle-wide reformatting with no behaviour change
Both mention build