Changes from 0.2.2 to 0.3.1 #230
ochafik
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all! We've just released
@modelcontextprotocol/ext-apps0.3.0 & 0.3.1 in rapid succession, here's what's changed since 0.2.2.Warning
Breaking changes:
viewporthas been replaced withcontainerDimensions— the new type distinguishes between fixed dimensions (height/width) and maximum constraints (maxHeight/maxWidth)PostMessageTransportnow requires an expliciteventSourceparameter to avoid accidentally omitting origin validationregisterAppToolsignature now aligns withserver.registerToolfrom the MCP TypeScript SDKHighlights
@modelcontextprotocolscope. Run directly vianpx @modelcontextprotocol/server-basic-react#184
app-with-depsbuild target enables loading the SDK directly from CDN in HTML apps #221API Changes
containerDimensions— Replacesviewportwith clearer semantics for fixed vs. maximum dimensions #153eventSourcerequired —PostMessageTransportconstructor now requires explicit event source to avoid accidentally omitting origin validation #208registerAppToolaligned — Signature now matchesserver.registerToolfrom the MCP TypeScript SDK #219ui.resourceUrioptional — Tools that need visibility but don't require a UI resource can now omit this #210toolInfo.idoptional — Aligned with spec; hosts can pass just the tool definition #216Platform & DX
safeAreaInsetssupport — Host context now includes safe area insets for proper handling of device notches and system UI #202npm startalias — Shorthand fornpm run examples:start#183Security
Bug Fixes
Promise.allSettled; one server failure no longer crashes the entire UI #206Full Changelog: v0.2.2...v0.3.1
Beta Was this translation helpful? Give feedback.
All reactions