fix: removing checksum

Author: jherr

CONTRIBUTING.md

@@ -20,6 +20,26 @@
 - Run `pnpm build` and `pnpm test` to make sure the changes work
 - Check your work and PR
 
+# Testing Your Changes
+
+When testing use `pnpm dev` at the top level of the `create-tsrouter-app` repo.
+
+Then from a peer directory use:
+
+```bash
+node ../create-tsrouter-app/cli/create-start-app/dist/index.js
+```
+
+To test `create-start-app` (or any of the CLIs).
+
+You can also do:
+
+```bash
+npm_config_user_agent=pnpm node ../create-tsrouter-app/cli/create-start-app/dist/index.js
+```
+
+If you want to specify a package manager.
+
 # Testing Add-ons and Starters
 
 Create the add-on or starter using the CLI. Then serve it locally from the project directory using `npx static-server`.

frameworks/react-cra/package.json

@@ -6,7 +6,6 @@
   "main": "./dist/index.js",
   "types": "./dist/types/index.d.ts",
   "scripts": {
-    "prebuild": "node ../../scripts/generate-checksums.js",
     "build": "tsc",
     "dev": "tsc --watch",
     "test": "eslint ./src && vitest run",

frameworks/react-cra/src/checksum.ts

@@ -7,8 +7,6 @@ import {
   scanProjectDirectory,
 } from '@tanstack/cta-engine'
 
-import { contentChecksum } from './checksum.js'
-
 import type { FrameworkDefinition } from '@tanstack/cta-engine'
 
 export function createFrameworkDefinition(): FrameworkDefinition {
@@ -47,12 +45,9 @@ export function createFrameworkDefinition(): FrameworkDefinition {
         forceTypescript: true,
       },
     },
-    contentChecksum,
   }
 }
 
 export function register() {
   registerFramework(createFrameworkDefinition())
 }
-
-export { contentChecksum }

frameworks/react-cra/src/index.ts

@@ -6,7 +6,6 @@
   "main": "./dist/index.js",
   "types": "./dist/types/index.d.ts",
   "scripts": {
-    "prebuild": "node ../../scripts/generate-checksums.js",
     "build": "tsc",
     "dev": "tsc --watch",
     "test": "eslint ./src && vitest run",

frameworks/solid/package.json

@@ -7,8 +7,6 @@ import {
   scanProjectDirectory,
 } from '@tanstack/cta-engine'
 
-import { contentChecksum } from './checksum.js'
-
 import type { FrameworkDefinition } from '@tanstack/cta-engine'
 
 export function createFrameworkDefinition(): FrameworkDefinition {
@@ -47,12 +45,9 @@ export function createFrameworkDefinition(): FrameworkDefinition {
         forceTypescript: true,
       },
     },
-    contentChecksum,
   }
 }
 
 export function register() {
   registerFramework(createFrameworkDefinition())
 }
-
-export { contentChecksum }

frameworks/solid/src/checksum.ts

@@ -160,7 +160,6 @@ export type FrameworkDefinition = {
       forceTypescript: boolean
     }
   >
-  contentChecksum?: string
 }
 
 export type Framework = Omit<FrameworkDefinition, 'base' | 'addOns'> &

frameworks/solid/src/index.ts

@@ -1,38 +1,8 @@
 # Scripts
 
-## generate-checksums.js
+This directory contains utility scripts for the project.
 
-This script generates checksums for the `react-cra` and `solid` frameworks to ensure version bumps when content changes.
-
-### Purpose
-
-The checksum system ensures that when any files in the following directories change, the framework package will have a different build output, triggering proper version bumping:
-
-- `add-ons/`
-- `examples/`
-- `hosts/`
-- `project/`
-- `toolchains/`
-
-### How It Works
-
-1. The script recursively scans all files in the specified directories
-2. Calculates a SHA-256 hash of all file contents and paths
-3. Generates `src/checksum.ts` in each framework with the exported checksum value
-4. The checksum is exported from `src/index.ts` and included in the built output
-
-### Integration
-
-The checksum generation runs automatically before each build via the `prebuild` script in:
-
-- `frameworks/react-cra/package.json`
-- `frameworks/solid/package.json`
-
-When running `pnpm build` at the root level, the checksums are automatically regenerated for both frameworks before TypeScript compilation.
-
-### Generated Files
-
-- `frameworks/react-cra/src/checksum.ts`
-- `frameworks/solid/src/checksum.ts`
-
-**Note:** These generated files should be committed to git as they are part of the package's public API and need to be tracked for proper version management.
+Available scripts:
+- `publish.js` - Publishing script
+- `check-outdated-packages.js` - Check for outdated packages
+- `check-for-ejs-duplicates.sh` - Check for duplicate EJS files