@sntlr/registry-shell 1.1.2 → 1.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sntlr/registry-shell",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.3",
|
|
4
4
|
"description": "Generic Next.js viewer for component registries. Drop a registry-shell.config.ts into your registry and get a full docs/components/blocks site on localhost:3000.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"shadcn",
|
|
@@ -48,6 +48,14 @@ const USER_PREVIEWS = resolveUserModule("components/previews", "fallback/preview
|
|
|
48
48
|
const nextConfig: NextConfig = {
|
|
49
49
|
output: process.env.BUILD_STANDALONE === "true" ? "standalone" : undefined,
|
|
50
50
|
|
|
51
|
+
// Next's file tracer figures out which node_modules files each
|
|
52
|
+
// serverless function needs. With pnpm (and our setup, where Next
|
|
53
|
+
// runs from inside node_modules), the tracer can't walk pnpm's
|
|
54
|
+
// virtual store without knowing the real project root. Point it at
|
|
55
|
+
// the user's project — that's the dir that contains `node_modules/.pnpm`
|
|
56
|
+
// on Vercel and any other pnpm-installed host.
|
|
57
|
+
...(USER_ROOT ? { outputFileTracingRoot: toPosix(USER_ROOT) } : {}),
|
|
58
|
+
|
|
51
59
|
// When installed as an external package (link:../registry-shell, npm, etc.),
|
|
52
60
|
// the shell's TSX lives under the user's node_modules and Next won't
|
|
53
61
|
// transpile it by default. The registry can list additional packages via
|