@idealyst/mcp-server 1.2.119 → 11.2.120

package/dist/index.js

@@ -7,7 +7,7 @@ import {
   storageGuides,
   toolDefinitions,
   translateGuides
-} from "./chunk-UD56HXN3.js";
+} from "./chunk-RVMPULO4.js";
 
 // src/index.ts
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
@@ -3128,17 +3128,23 @@ navigator.navigate({ path: '/new-location', replace: true });
 
 ## useParams Hook
 
-Access current route path parameters. Returns \`Record<string, string>\`.
+Access current route path parameters. Returns \`Record<string, string | undefined>\`.
 
 > **WARNING:** \`useParams()\` does NOT accept generic type arguments. Do NOT write \`useParams<{ id: string }>()\` \u2014 this causes TS2558. Access params by key from the returned record instead.
 
+> **IMPORTANT:** Param values are \`string | undefined\`, NOT \`string\`. When passing a param to a function that expects \`string\`, you MUST handle the undefined case \u2014 either with a fallback (\`params.id ?? ''\`), a guard (\`if (!params.id) return null\`), or a non-null assertion (\`params.id!\`) if you are certain it exists. Without this, TypeScript will report TS2345.
+
 \`\`\`tsx
 import { useParams } from '@idealyst/navigation';
 
 function UserScreen() {
   // CORRECT \u2014 no type argument
   const params = useParams();
-  const userId = params.id;        // Path param from /user/:id
+  const userId = params.id;        // string | undefined from /user/:id
+
+  // Handle undefined before using in typed contexts:
+  if (!userId) return <Text>User not found</Text>;
+  // Now userId is narrowed to string
 
   // WRONG \u2014 useParams does NOT accept generics
   // const params = useParams<{ id: string }>();  // TS2558 error!
@@ -3149,26 +3155,37 @@ function UserScreen() {
 
 ## useNavigationState Hook
 
-Access navigation state passed via the \`state\` property:
+Access navigation state passed via the \`state\` property.
+
+> **IMPORTANT \u2014 Type constraints:**
+> - \`navigate({ state: {...} })\` requires all values to be \`string | number | boolean\` \u2014 NO \`undefined\` or \`null\`. Do NOT spread objects that may contain undefined values.
+> - \`useNavigationState<T>()\` requires \`T extends Record<string, unknown>\`. Use \`Record<string, string | number | boolean>\` for the type parameter, or a specific interface with NON-optional fields.
+> - **Do NOT use optional fields (\`?\`) in the type parameter** \u2014 values passed via state are always present (they were explicitly set by navigate()). Use required fields instead.
 
 \`\`\`tsx
 import { useNavigationState } from '@idealyst/navigation';
 
-// When navigating:
+// When navigating \u2014 all values must be string | number | boolean:
 navigator.navigate({
   path: '/recording',
   state: { autostart: true, source: 'home' }
 });
 
-// In destination screen:
+// In destination screen \u2014 use REQUIRED fields (not optional):
 function RecordingScreen() {
-  const { autostart, source } = useNavigationState<{
-    autostart?: boolean;
-    source?: string;
+  const state = useNavigationState<{
+    autostart: boolean;
+    source: string;
   }>();
 
-  // autostart = true, source = 'home'
+  // state.autostart = true, state.source = 'home'
 }
+
+// For multi-step wizards, pass ALL accumulated data as required fields:
+navigator.navigate({
+  path: '/step3',
+  state: { firstName: name, lastName: last, theme: selectedTheme }
+});
 \`\`\`
 
 ### Consuming State (Web)