@workday/canvas-kit-mcp 15.0.0-alpha.0023-next.0 → 15.0.0-alpha.0032-next.0

package/dist/lib/upgrade-guides/14.0-UPGRADE-GUIDE.md

@@ -651,29 +651,40 @@ instead.
 Previously, the `usePopupStack` hook created a CSS class name that was passed to our Popups. We attached those theme styles to that class name. This allowed the theme to be available in our Popups. But it also created a cascade barrier that blocked the global theme from being applied to our Popup components.
 Because we now use global CSS variables, we no longer need this class name to provide the global theme to Popups. But we have to remove this generated class name to allow the global theme to be applied to Popups.
 
-> **Important:** Passing a `theme` to the `CanvasProvider` **will not** theme components in Modals
-> and Dialogs. You can either pass a `className` or define CSS variables at the root.
+If you want to have scoped theming where a part of your application needs different theming, you can
+still do this via the `theme` prop.
 
-**Before in v13**
+> **Note:** Only the properties of the theme object that are changed will be forward to popups and
+> modals. IE, if you change theme.palette.primary.main, only those tokens will change for popups and
+> modals.
+
+#### Scoped Theming vs Global Theming
+
+**Only** use the `theme` prop on the `CanvasProvider` if you intentionally want to theme part of
+your application that is different from global theming.
+
+**Scoped Theming**
 
 ```tsx
-// When passing a theme to the Canvas Provider, the `usePopupStack` would grab the theme and generate a class to forward the theme to Modals and Dialogs. This would create a cascade barrier for any CSS variables deinfed at the root.
-<CanvasProvider theme={{canvas: {palette: {primary: {main: 'blue'}}}}}>
-  <Modal>//... rest of modal code</Modal>
+
+<CanvasProvider theme={{canvas: {palette: {primary: {main: 'teal'}}}}}>
+ {//part of your app to have different theme from the rest of your application}
 </CanvasProvider>
 ```
 
-**After in v14**
+> **Important:** Use the `theme` prop on the `CanvasProvider` if you intentionally want to theme
+> part of your application that is different from global theming.
+
+**Global Theming**
 
 ```tsx
-// If you wish to still theme you application and Modals, you can either define the CSS variables at the root level of your application or define a className and pass it to the CanvasProvider.
-:root {
- --cnvs-brand-primary-base: blue;
-}
+import '@workday/canvas-tokens-web/css/base/_variables.css';
+import '@workday/canvas-tokens-web/css/brand/_variables.css';
+import '@workday/canvas-tokens-web/css/system/_variables.css';
 
 <CanvasProvider>
-  <Modal>//... rest of modal code</Modal>
-</CanvasProvider>
+  <App />
+</CanvasProvider>;
 ```
 ### Search Form (Labs) 🚨
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@workday/canvas-kit-mcp",
-  "version": "15.0.0-alpha.0023-next.0",
+  "version": "15.0.0-alpha.0032-next.0",
   "description": "MCP package for Canvas Kit",
   "author": "Workday, Inc. (https://www.workday.com)",
   "license": "Apache-2.0",
@@ -32,7 +32,7 @@
   "scripts": {
     "build:copy": "tsx ./build/index.ts",
     "build:types": "tsc --project tsconfig.build.json -d true --declarationDir dist/types --emitDeclarationOnly --pretty",
-    "build:mcp": "esbuild lib/index.ts --bundle --platform=node --outfile=dist/index.js --format=esm --sourcemap && esbuild lib/cli.ts --bundle --platform=node --outfile=dist/cli.js --format=esm --sourcemap",
+    "build:mcp": "esbuild lib/index.ts --bundle --platform=node --packages=external --outfile=dist/index.js --format=esm --sourcemap && esbuild lib/cli.ts --bundle --platform=node --packages=external --outfile=dist/cli.js --format=esm --sourcemap",
     "build": "npm-run-all build:copy build:types build:mcp",
     "clean": "rimraf dist && rimraf .build-info && mkdirp dist"
   },
@@ -53,5 +53,5 @@
     "tsx": "^4.7.0",
     "typescript": "5.0"
   },
-  "gitHead": "13b3abf5b4752be5738a78f3c37e31b6252077dc"
+  "gitHead": "f48e25e031c1287c7d5160ef76a8746fe726de1c"
 }