create-nextly-app 0.0.2-alpha.56 → 0.0.2-alpha.58

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.mjs CHANGED
@@ -1,5 +1,5 @@
1
1
  import { createRequire } from 'module';
2
- export { createNextly } from './chunk-6434MGWG.mjs';
2
+ export { createNextly } from './chunk-E6IFBI6N.mjs';
3
3
 
4
4
  createRequire(import.meta.url);
5
5
  //# sourceMappingURL=index.mjs.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-nextly-app",
3
- "version": "0.0.2-alpha.56",
3
+ "version": "0.0.2-alpha.58",
4
4
  "description": "CLI to scaffold Nextly in your Next.js project",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -42,12 +42,12 @@
42
42
  "typescript": "^5.9.3",
43
43
  "vite-tsconfig-paths": "^5.1.4",
44
44
  "vitest": "^4.1.0",
45
- "@nextlyhq/eslint-config": "0.0.2-alpha.56",
46
- "@nextlyhq/tsconfig": "0.0.2-alpha.56",
47
- "@nextlyhq/telemetry": "0.0.2-alpha.56"
45
+ "@nextlyhq/eslint-config": "0.0.2-alpha.58",
46
+ "@nextlyhq/telemetry": "0.0.2-alpha.58",
47
+ "@nextlyhq/tsconfig": "0.0.2-alpha.58"
48
48
  },
49
49
  "engines": {
50
- "node": ">=20.0.0"
50
+ "node": "^20.19.0 || ^22.12.0 || >=24.0.0"
51
51
  },
52
52
  "keywords": [
53
53
  "nextly",
@@ -0,0 +1,42 @@
1
+ # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2
+
3
+ # dependencies
4
+ /node_modules
5
+ /.pnp
6
+ .pnp.*
7
+ .yarn/*
8
+ !.yarn/patches
9
+ !.yarn/plugins
10
+ !.yarn/releases
11
+ !.yarn/versions
12
+
13
+ # testing
14
+ /coverage
15
+
16
+ # next.js
17
+ /.next/
18
+ /out/
19
+
20
+ # production
21
+ /build
22
+
23
+ # misc
24
+ .DS_Store
25
+ *.pem
26
+
27
+ # debug
28
+ npm-debug.log*
29
+ yarn-debug.log*
30
+ yarn-error.log*
31
+ .pnpm-debug.log*
32
+
33
+ # env files (can opt-in for committing if needed)
34
+ .env*
35
+ !.env.example
36
+
37
+ # vercel
38
+ .vercel
39
+
40
+ # typescript
41
+ *.tsbuildinfo
42
+ next-env.d.ts
@@ -1,5 +1,15 @@
1
1
  @import "tailwindcss";
2
2
 
3
+ /* The families the imported font stylesheets declare, bound to the variables the rules
4
+ below read. Named here rather than by `next/font`, which used to inject them: the faces
5
+ now arrive as ordinary stylesheets, so the binding has to be written down somewhere, and
6
+ the name is load-bearing — the admin theme reads `--font-geist`. Quoted family names, so
7
+ the two-word values stay one identifier. */
8
+ :root {
9
+ --font-geist: "Geist Variable";
10
+ --font-geist-mono: "Geist Mono Variable";
11
+ }
12
+
3
13
  :root {
4
14
  --background: #ffffff;
5
15
  --foreground: #171717;
@@ -8,8 +18,11 @@
8
18
  @theme inline {
9
19
  --color-background: var(--background);
10
20
  --color-foreground: var(--foreground);
11
- --font-sans: var(--font-geist-sans);
12
- --font-mono: var(--font-geist-mono);
21
+ /* Fallback arguments, not a trailing family list: an unresolved var() with no
22
+ fallback invalidates the whole declaration rather than falling through to
23
+ what comes after the closing paren. */
24
+ --font-sans: var(--font-geist, ui-sans-serif), system-ui, sans-serif;
25
+ --font-mono: var(--font-geist-mono, ui-monospace), monospace;
13
26
  }
14
27
 
15
28
  @media (prefers-color-scheme: dark) {
@@ -1,16 +1,31 @@
1
1
  import type { Metadata } from "next";
2
- import { Geist, Geist_Mono } from "next/font/google";
2
+ import "@fontsource-variable/geist";
3
+ import "@fontsource-variable/geist-mono";
3
4
  import "./globals.css";
4
5
 
5
- const geistSans = Geist({
6
- variable: "--font-geist-sans",
7
- subsets: ["latin"],
8
- });
9
-
10
- const geistMono = Geist_Mono({
11
- variable: "--font-geist-mono",
12
- subsets: ["latin"],
13
- });
6
+ /**
7
+ * The faces are imported as STYLESHEETS from packages in `node_modules`, rather
8
+ * than fetched from fonts.googleapis.com by `next/font/google` while
9
+ * `next build` runs — which made every build depend on reaching a third party
10
+ * and fail behind a proxy, on a locked-down runner, or offline.
11
+ *
12
+ * A bare package import rather than `next/font/local` pointing INTO
13
+ * `node_modules`: a literal path asserts where the package physically lives,
14
+ * and that assertion is false under Yarn's Plug'n'Play linker (no
15
+ * `node_modules` at all), under npm/Yarn workspace hoisting (the package moves
16
+ * to the workspace root), and under pnpm's own symlinked store. An import asks
17
+ * the resolver instead, which is correct under every layout.
18
+ *
19
+ * The trade is `next/font`'s metric-adjusted fallback, so text can shift
20
+ * slightly as the face arrives. The families are bound to this app's `--font-*`
21
+ * variables in `globals.css`, which is what every rule downstream reads. *
22
+ * Importing the package root ships every subset the face offers — Latin, Latin
23
+ * Extended, Cyrillic, Vietnamese — but each `@font-face` carries a
24
+ * `unicode-range`, so a browser downloads only the subsets the page actually
25
+ * uses. The deployed bundle is larger than a single hand-picked file; what a
26
+ * reader fetches is not, and a page in Cyrillic now gets its face instead of a
27
+ * fallback.
28
+ */
14
29
 
15
30
  /**
16
31
  * `metadataBase` tells Next.js how to resolve relative URLs in OpenGraph
@@ -32,12 +47,12 @@ export default function RootLayout({
32
47
  children: React.ReactNode;
33
48
  }>) {
34
49
  return (
50
+ // The font variables belong on <html>: the admin theme declares --font-sans
51
+ // in a non-inline @theme, which emits it into :root and resolves the
52
+ // reference THERE. A variable exposed lower down, on <body>, is invisible to
53
+ // that declaration however it is spelled.
35
54
  <html lang="en" suppressHydrationWarning>
36
- <body
37
- className={`${geistSans.variable} ${geistMono.variable} antialiased`}
38
- >
39
- {children}
40
- </body>
55
+ <body className="antialiased">{children}</body>
41
56
  </html>
42
57
  );
43
58
  }
@@ -21,7 +21,13 @@
21
21
  "paths": {
22
22
  "@/*": ["./src/*"],
23
23
  "@/components/*": ["./src/app/(frontend)/components/*"],
24
- "@nextly-config": ["./nextly.config.ts"]
24
+ "@nextly-config": ["./nextly.config.ts"],
25
+ // Pagefind's browser bundle is generated into public/ at build time, so it
26
+ // is imported by URL and cannot be resolved on disk while type-checking.
27
+ // A `declare module` cannot describe it either: TypeScript treats a rooted
28
+ // specifier as relative and rejects the declaration (TS2436). Templates
29
+ // without a search page simply never import it, leaving this mapping inert.
30
+ "/pagefind/pagefind.js": ["./src/types/pagefind.d.ts"]
25
31
  }
26
32
  },
27
33
  "include": [
@@ -1,5 +1,25 @@
1
1
  @import "tailwindcss";
2
2
 
3
+ /* The families the imported font stylesheets declare, bound to the variables the rules
4
+ below read. Named here rather than by `next/font`, which used to inject them: the faces
5
+ now arrive as ordinary stylesheets, so the binding has to be written down somewhere, and
6
+ the name is load-bearing — the admin theme reads `--font-geist`. Quoted family names, so
7
+ the two-word values stay one identifier. */
8
+ :root {
9
+ /* `--font-geist` and `--font-geist-mono` are the names the ADMIN theme reads
10
+ (`--font-sans: var(--font-geist, Geist), ...` in a non-inline `@theme`, so
11
+ it resolves at `:root`). A template that loads a different face still has to
12
+ expose it under these names or the admin renders in a system fallback while
13
+ the app's own pages render correctly. */
14
+ --font-geist: "Inter Variable";
15
+ --font-geist-mono: "JetBrains Mono Variable";
16
+ /* This template's own display face, read by `.font-display` below. NOT named
17
+ `--font-mono` for its mono face: that is the theme's OWN token, declared at
18
+ `:root`, and redefining it here replaces the theme's whole fallback chain
19
+ rather than feeding it. */
20
+ --font-display: "Inter Variable";
21
+ }
22
+
3
23
  /**
4
24
  * Blank-template global styles.
5
25
  *
@@ -28,6 +48,18 @@
28
48
  --color-foreground: #f9fafb;
29
49
  }
30
50
 
51
+ /* `@theme inline` on purpose, and it is the whole point of this block. An inline theme
52
+ SUBSTITUTES the value where the utility is used; a plain `@theme` emits the variable into
53
+ `:root`, which is where `@nextlyhq/admin` declares its own `--font-mono` — redefining it there
54
+ would replace the admin's entire fallback chain with this one family.
55
+
56
+ Needed because the frontend routes do not load the admin stylesheet, so nothing else binds the
57
+ `font-mono` utility this template uses on its badge and file-path text; without it they fall
58
+ back to Tailwind's default mono rather than the face the template loads. */
59
+ @theme inline {
60
+ --font-mono: var(--font-geist-mono, ui-monospace), monospace;
61
+ }
62
+
31
63
  @theme {
32
64
  --color-background: var(--color-background);
33
65
  --color-foreground: var(--color-foreground);
@@ -67,7 +99,11 @@ body {
67
99
  }
68
100
 
69
101
  .font-display {
70
- font-family: var(--font-display), ui-sans-serif, system-ui, sans-serif;
102
+ /* The generic families are the var()'s fallback argument rather than a list
103
+ after it: an unresolved var() with no fallback invalidates the whole
104
+ declaration, so the element would inherit its parent's face instead of
105
+ falling through to these. */
106
+ font-family: var(--font-display, ui-sans-serif), system-ui, sans-serif;
71
107
  }
72
108
 
73
109
  .btn-primary {
@@ -1,19 +1,32 @@
1
1
  import type { Metadata } from "next";
2
- import { Inter, JetBrains_Mono } from "next/font/google";
2
+ import "@fontsource-variable/inter";
3
+ import "@fontsource-variable/jetbrains-mono";
3
4
 
4
5
  import "./globals.css";
5
6
 
6
- const display = Inter({
7
- variable: "--font-display",
8
- subsets: ["latin"],
9
- display: "swap",
10
- });
11
-
12
- const mono = JetBrains_Mono({
13
- variable: "--font-mono",
14
- subsets: ["latin"],
15
- display: "swap",
16
- });
7
+ /**
8
+ * The faces are imported as STYLESHEETS from packages in `node_modules`, rather
9
+ * than fetched from fonts.googleapis.com by `next/font/google` while
10
+ * `next build` runs — which made every build depend on reaching a third party
11
+ * and fail behind a proxy, on a locked-down runner, or offline.
12
+ *
13
+ * A bare package import rather than `next/font/local` pointing INTO
14
+ * `node_modules`: a literal path asserts where the package physically lives,
15
+ * and that assertion is false under Yarn's Plug'n'Play linker (no
16
+ * `node_modules` at all), under npm/Yarn workspace hoisting (the package moves
17
+ * to the workspace root), and under pnpm's own symlinked store. An import asks
18
+ * the resolver instead, which is correct under every layout.
19
+ *
20
+ * The trade is `next/font`'s metric-adjusted fallback, so text can shift
21
+ * slightly as the face arrives. The families are bound to this app's `--font-*`
22
+ * variables in `globals.css`, which is what every rule downstream reads. *
23
+ * Importing the package root ships every subset the face offers — Latin, Latin
24
+ * Extended, Cyrillic, Vietnamese — but each `@font-face` carries a
25
+ * `unicode-range`, so a browser downloads only the subsets the page actually
26
+ * uses. The deployed bundle is larger than a single hand-picked file; what a
27
+ * reader fetches is not, and a page in Cyrillic now gets its face instead of a
28
+ * fallback.
29
+ */
17
30
 
18
31
  /**
19
32
  * Blank-template root layout.
@@ -38,9 +51,7 @@ export default function RootLayout({
38
51
  }>) {
39
52
  return (
40
53
  <html lang="en" suppressHydrationWarning>
41
- <body className={`${display.variable} ${mono.variable} antialiased`}>
42
- {children}
43
- </body>
54
+ <body className="antialiased">{children}</body>
44
55
  </html>
45
56
  );
46
57
  }
@@ -0,0 +1,10 @@
1
+ node_modules
2
+ dist
3
+ *.log
4
+
5
+ # Embedded dev playground — never published, never committed build output
6
+ dev/.next
7
+ dev/*.db
8
+ dev/*.db-journal
9
+ .env
10
+ .env.local