create-harper 1.9.2 → 1.10.1

package/lib/constants/renameFiles.js

@@ -6,6 +6,7 @@ export const renameFiles = {
 	'_env': '.env',
 	'_env.example': '.env.example',
 	_aiignore: '.aiignore',
+	_claude: '.claude',
 	_github: '.github',
 	_gitignore: '.gitignore',
 	_nvmrc: '.nvmrc',

package/lib/init.js

@@ -76,7 +76,7 @@ export async function init() {
 		// Write out the contents based on all prior steps.
 		const cwd = process.cwd();
 		const root = path.join(cwd, targetDir);
-		scaffoldProject(root, projectName, packageName, template, envVars);
+		scaffoldProject(root, projectName, packageName, template, envVars, pkgManager);
 
 		// Log out the next steps.
 		installAndOptionallyStart(root, pkgManager, immediate, args.skipInstall, selectedSkills, selectedAgents);

package/lib/steps/scaffoldProject.js

@@ -12,8 +12,9 @@ import { crawlTemplateDir } from '../fs/crawlTemplateDir.js';
  * @param {string} packageName - The name for the package.json.
  * @param {string} template - The template name to use.
  * @param {import('./getEnvVars.js').EnvVars} [envVars] - Environment variables to substitute.
+ * @param {string} [pkgManager] - The package manager that invoked us (e.g. npm, pnpm, yarn, bun). Defaults to npm.
  */
-export function scaffoldProject(root, projectName, packageName, template, envVars) {
+export function scaffoldProject(root, projectName, packageName, template, envVars, pkgManager) {
 	fs.mkdirSync(root, { recursive: true });
 	prompts.log.step(`Scaffolding project in ${root}...`);
 
@@ -21,6 +22,7 @@ export function scaffoldProject(root, projectName, packageName, template, envVar
 		'your-project-name-here': projectName || 'your-project-name-here',
 		'your-package-name-here': packageName || 'your-package-name-here',
 		'your-fabric.harper.fast-cluster-url-here': envVars?.target || 'your-fabric.harper.fast-cluster-url-here',
+		'your-package-manager-here': pkgManager || 'npm',
 		'\n\t"repository": "github:HarperFast/create-harper",': '',
 	};
 

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "create-harper",
 	"description": "Scaffold a new Harper project in JavaScript or TypeScript.",
-	"version": "1.9.2",
+	"version": "1.10.1",
 	"type": "module",
 	"sideEffects": false,
 	"exports": {

package/template-react/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-react-ssr/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-react-ssr/src/entry-server.jsx

@@ -3,8 +3,26 @@ import { StrictMode } from 'react';
 import { renderToString } from 'react-dom/server';
 
 /**
- * Server render entry. The Vite Harper plugin calls this for HTML navigations and injects the
- * returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ * Server render entry. The Vite Harper plugin calls this (awaiting it) for HTML navigations and
+ * injects the returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ *
+ * To render with data already in place (no client-side fetch), read from Harper right here. The
+ * `tables` registry is the same live, process-wide object available everywhere in Harper — the SSR
+ * entry can reach it via `import { tables } from 'harper'` because Harper symlinks
+ * `node_modules/harper` to the running install (and `vite.config.js` keeps `harper` external). Make
+ * `render` async and query a table, e.g.:
+ *
+ *     import { tables } from 'harper';
+ *
+ *     // The template's App takes no props — update App.jsx to accept `product`.
+ *     export async function render(url) {
+ *       const product = await tables.Product.get(idFromUrl(url));
+ *       return renderToString(
+ *         <StrictMode>
+ *           <App product={product} />
+ *         </StrictMode>,
+ *       );
+ *     }
  *
  * @param {string} _url The request URL — use it to drive routing/data loading per request.
  * @returns {string}

package/template-react-ssr/vite.config.js

@@ -12,6 +12,13 @@ export default defineConfig({
 			'@': path.resolve(import.meta.dirname, './src'),
 		},
 	},
+	ssr: {
+		// Keep `harper` external so the SSR entry resolves it to Harper's running runtime instead of
+		// bundling it. `node_modules/harper` is symlinked to the running install, and symlinked deps
+		// aren't reliably auto-externalized for SSR — this is what lets `import { tables } from 'harper'`
+		// in entry-server read live data. See src/entry-server.jsx.
+		external: ['harper'],
+	},
 	build: {
 		outDir: 'dist',
 		emptyOutDir: true,

package/template-react-ts/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-react-ts-ssr/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-react-ts-ssr/src/entry-server.tsx

@@ -3,8 +3,26 @@ import { StrictMode } from 'react';
 import { renderToString } from 'react-dom/server';
 
 /**
- * Server render entry. The Vite Harper plugin calls this for HTML navigations and injects the
- * returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ * Server render entry. The Vite Harper plugin calls this (awaiting it) for HTML navigations and
+ * injects the returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ *
+ * To render with data already in place (no client-side fetch), read from Harper right here. The
+ * `tables` registry is the same live, process-wide object available everywhere in Harper — the SSR
+ * entry can reach it via `import { tables } from 'harper'` because Harper symlinks
+ * `node_modules/harper` to the running install (and `vite.config.ts` keeps `harper` external). Make
+ * `render` async and query a table, e.g.:
+ *
+ *     import { tables } from 'harper';
+ *
+ *     // The template's App takes no props — update App.tsx to accept `product`.
+ *     export async function render(url: string): Promise<string> {
+ *       const product = await tables.Product.get(idFromUrl(url));
+ *       return renderToString(
+ *         <StrictMode>
+ *           <App product={product} />
+ *         </StrictMode>,
+ *       );
+ *     }
  *
  * @param _url The request URL — use it to drive routing/data loading per request.
  */

package/template-react-ts-ssr/vite.config.ts

@@ -12,6 +12,13 @@ export default defineConfig({
 			'@': path.resolve(import.meta.dirname, './src'),
 		},
 	},
+	ssr: {
+		// Keep `harper` external so the SSR entry resolves it to Harper's running runtime instead of
+		// bundling it. `node_modules/harper` is symlinked to the running install, and symlinked deps
+		// aren't reliably auto-externalized for SSR — this is what lets `import { tables } from 'harper'`
+		// in entry-server read live data. See src/entry-server.tsx.
+		external: ['harper'],
+	},
 	build: {
 		outDir: 'dist',
 		emptyOutDir: true,

package/template-vanilla/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-vanilla-ts/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-vue/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-vue-ssr/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-vue-ts/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}

package/template-vue-ts-ssr/_claude/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.0.1",
+	"configurations": [
+		{
+			"name": "harper",
+			"runtimeExecutable": "your-package-manager-here",
+			"runtimeArgs": ["run", "dev"],
+			"port": 9926
+		}
+	]
+}