After upgrading to Next.js 16.2.1 (after canary builds that included #90907), import { type X } from a server-only module inside a "use client" component now throws a boundary error.

Fix Plan

To resolve the issue, you need to refactor your code to avoid importing server-only modules into client components. Here are the steps:

• Create a new file for the shared type, e.g., types.ts:

// types.ts export type MyType = boolean;

*   Import the shared type in both the server and client components:
    ```tsx
// lib/server.ts
import type { MyType } from "@/types";

// components/client.tsx
import type { MyType } from "@/types";

• Ensure that the types.ts file does not import any server-only modules.

Verification

After applying the fix, verify that the error is resolved by running next dev and checking the console for any errors. The application should compile and run without any issues related to importing server-only modules into client components.

Extra Tips

• Make sure to keep server-only logic separate from client-side code to avoid similar issues in the future.
• Consider using a linter or code analyzer to detect and prevent such issues early in the development process.
• If you're using a monorepo or a complex project structure, ensure that your tsconfig.json files are properly configured to handle the different environments and module types.