@vexcms/next 0.1.0-alpha.24 → 0.1.0-alpha.26
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/dist/index.js.map +1 -1
- package/package.json +3 -3
package/dist/index.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"sources":["../src/index.ts"],"sourcesContent":["// @vexcms/next v0.1.0-alpha.1\n//\n// Two distinct export surfaces:\n//\n// 1. Server / client component entries (sub-path imports — required because\n// \"use client\" can't be mixed with async server components in one bundle):\n// import { NextAdminPage } from \"@vexcms/next/server\" ← async server component\n// import { NextAdminLayout } from \"@vexcms/next/client\" ← \"use client\" component\n//\n// 2. Config / type re-exports (everything below). Re-exports `@vexcms/react`'s\n// HKT-bound config functions and types transitively so Next consumers can\n// import every config function from a single package:\n//\n// import {\n// defineConfig,\n// defineCollection,\n// relationship,\n// text, number, select, date, url, checkbox,\n// } from \"@vexcms/next\";\n//\n// `admin.components.preview` slots remain typed as React `ComponentType<P>`\n// via `ReactHKT` because @vexcms/react bound it before re-exporting. See\n// spec 22 Decision 15 for the architectural rationale.\n\n// Server / client surface\nexport * from \"./NextAdminPage\";\nexport * from \"./NextAdminLayout\";\n\n// Config functions — HKT-bound wrappers from @vexcms/react\nexport { relationship, defineCollection } from \"@vexcms/react\";\n\n// Field config functions without component slots (pure pass-through)\nexport {\n text,\n number,\n select,\n date,\n url,\n checkbox,\n defineConfig,\n} from \"@vexcms/react\";\n\n// Public types — HKT-bound where applicable.\n// `*FieldInput` core config types intentionally not re-exported (they collide\n// with React `*FieldInput` component names; users get them via inference\n// through the config functions).\nexport type {\n AdminUser,\n // HKT-bound (admin.components.preview = React ComponentType)\n RelationshipFieldInput,\n RelationshipField,\n AdminCollectionConfigInput,\n CollectionConfigInput,\n CollectionConfig,\n // Resolved field types\n TextField,\n NumberField,\n SelectField,\n DateField,\n UrlField,\n CheckboxField,\n // Shared types\n AdminField,\n CollectionSlug,\n VexDocument,\n VexConfig,\n VexClientConfig,\n VexClientConfigInput,\n VexServerConfigInput,\n RelationshipPreviewProps,\n} from \"@vexcms/react\";\n\n// API functions are NOT re-exported from this barrel because @vexcms/next's\n// root index.ts is imported by server components (NextAdminPage). Pulling\n// @vexcms/
|
|
1
|
+
{"version":3,"sources":["../src/index.ts"],"sourcesContent":["// @vexcms/next v0.1.0-alpha.1\n//\n// Two distinct export surfaces:\n//\n// 1. Server / client component entries (sub-path imports — required because\n// \"use client\" can't be mixed with async server components in one bundle):\n// import { NextAdminPage } from \"@vexcms/next/server\" ← async server component\n// import { NextAdminLayout } from \"@vexcms/next/client\" ← \"use client\" component\n//\n// 2. Config / type re-exports (everything below). Re-exports `@vexcms/react`'s\n// HKT-bound config functions and types transitively so Next consumers can\n// import every config function from a single package:\n//\n// import {\n// defineConfig,\n// defineCollection,\n// relationship,\n// text, number, select, date, url, checkbox,\n// } from \"@vexcms/next\";\n//\n// `admin.components.preview` slots remain typed as React `ComponentType<P>`\n// via `ReactHKT` because @vexcms/react bound it before re-exporting. See\n// spec 22 Decision 15 for the architectural rationale.\n\n// Server / client surface\nexport * from \"./NextAdminPage\";\nexport * from \"./NextAdminLayout\";\n\n// Config functions — HKT-bound wrappers from @vexcms/react\nexport { relationship, defineCollection } from \"@vexcms/react\";\n\n// Field config functions without component slots (pure pass-through)\nexport {\n text,\n number,\n select,\n date,\n url,\n checkbox,\n defineConfig,\n} from \"@vexcms/react\";\n\n// Public types — HKT-bound where applicable.\n// `*FieldInput` core config types intentionally not re-exported (they collide\n// with React `*FieldInput` component names; users get them via inference\n// through the config functions).\nexport type {\n AdminUser,\n // HKT-bound (admin.components.preview = React ComponentType)\n RelationshipFieldInput,\n RelationshipField,\n AdminCollectionConfigInput,\n CollectionConfigInput,\n CollectionConfig,\n // Resolved field types\n TextField,\n NumberField,\n SelectField,\n DateField,\n UrlField,\n CheckboxField,\n // Shared types\n AdminField,\n CollectionSlug,\n VexDocument,\n VexConfig,\n VexClientConfig,\n VexClientConfigInput,\n VexServerConfigInput,\n RelationshipPreviewProps,\n} from \"@vexcms/react\";\n\n// API functions are NOT re-exported from this barrel because @vexcms/next's\n// root index.ts is imported by server components (NextAdminPage). Pulling\n// @vexcms/react/client here would transitively import @convex-dev/react-query\n// which uses createContext — crashing RSC.\n//\n// Import directly from the correct environment-specific path instead:\n//\n// import { find, get, search } from \"@vexcms/react/client\"; ← React components\n// import { find, get, search } from \"@vexcms/core/server\"; ← Convex handlers\n\nexport type {\n RelationshipKeysOf,\n TextKeysOf,\n SortableKeysOf,\n RelationshipTargetOf,\n Populated,\n PopulateShape,\n} from \"@vexcms/core\";\n\n// Cache / SEO surface — server-only, no client context, so these are safe in\n// this RSC-imported root barrel. Also reachable via the \"@vexcms/next/cache\"\n// and \"@vexcms/next/seo\" subpaths.\nexport { createVexServerClient } from \"./cache/createVexServerClient\";\nexport type { VexServerClientOptions, VexServerClient } from \"./cache/types\";\nexport { createVexRobots } from \"./seo/createVexRobots\";\nexport { createVexSitemap } from \"./seo/createVexSitemap\";\nexport { vexMetadata } from \"./seo/vexMetadata\";\nexport { vexStaticParams } from \"./seo/vexStaticParams\";\nexport { createVexRevalidateRoute } from \"./cache/createVexRevalidateRoute\";\nexport type { CreateVexRevalidateRouteProps } from \"./cache/createVexRevalidateRoute\";\nexport type {\n} from \"./cache/types\";\n"],"mappings":";;;;;;;;;;;;;;;;;;AA6BA,SAAS,cAAc,wBAAwB;AAG/C;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,OACK;","names":[]}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vexcms/next",
|
|
3
|
-
"version": "0.1.0-alpha.
|
|
3
|
+
"version": "0.1.0-alpha.26",
|
|
4
4
|
"description": "Next.js adapter and admin routes for VexCMS",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"cms",
|
|
@@ -66,8 +66,8 @@
|
|
|
66
66
|
},
|
|
67
67
|
"dependencies": {
|
|
68
68
|
"lucide-react": "0.577.0",
|
|
69
|
-
"@vexcms/core": "0.1.0-alpha.
|
|
70
|
-
"@vexcms/react": "0.1.0-alpha.
|
|
69
|
+
"@vexcms/core": "0.1.0-alpha.26",
|
|
70
|
+
"@vexcms/react": "0.1.0-alpha.26"
|
|
71
71
|
},
|
|
72
72
|
"devDependencies": {
|
|
73
73
|
"@convex-dev/react-query": "0.1.0",
|