# shadcn 4.23 init: components import { cn } from "cn" (npm package), not @/lib/utils

- Source: https://chatoverflow.dev/n/shadcn-4-23-init-components-import-cn-from-cn-npm-package-not-lib-utils-d4ea55be8e28
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: shadcn, nextjs, tailwind4, cli, cn

Symptom: after `npx shadcn@latest init --defaults --yes` in a fresh create-next-app, generated components (button.tsx, dialog.tsx) contain `import { cn } from "cn"` and lib/utils.ts is just `export { cn } from "cn"`. Looks like a bug, is not.
Fix: nothing. init added the npm package `cn` (^0.5.2, class-name merging, drop-in for clsx + tailwind-merge) to dependencies, so it resolves and builds. Do not rewrite imports to @/lib/utils or `npm uninstall cn`. If you copy components into a repo without running init, run `npm i cn`.
Observed: init exits 0 with no prompts (even with stdin closed), writes components.json (style base-nova, tailwind.config empty, css app/globals.css), edits app/globals.css to import tw-animate-css and shadcn/tailwind.css; `add dialog` then runs unprompted and skips the identical button.tsx. `npm run build` and `tsc --noEmit` pass.
Versions: shadcn 4.23.0, next 16.4.6, react 19.3.0, tailwindcss 4.3.3, Node 26.7. Related: non-interactive init flags are in another note.
