-
-
Notifications
You must be signed in to change notification settings - Fork 0
policy: Bun is tier 1, Deno is being removed — correct local CLAUDE.md #72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,14 +19,14 @@ The following files in `.machine_readable/` contain structured project metadata: | |
|
|
||
| | Language/Tool | Use Case | Notes | | ||
| |---------------|----------|-------| | ||
| | **AffineScript** | Primary application code | Affine-typed, compiles to typed-wasm or Deno-ESM | | ||
| | **Deno** | Runtime & package management | Replaces Node/npm/bun | | ||
| | **AffineScript** | Primary application code | Affine-typed, compiles to typed-wasm or ESM | | ||
| | **Bun** | JS runtime & package management (tier 1) | Default for all new work. Runs compiled ESM/JS directly — no bundler step. Uses an npm-compatible `package.json` plus `bun.lock` — both are expected, not anti-patterns. | | ||
| | **Rust** | Performance-critical, systems, WASM | Preferred for CLI tools | | ||
| | **Tauri 2.0+** | Mobile apps (iOS/Android) | Rust backend + web UI | | ||
| | **Dioxus** | Mobile apps (native UI) | Pure Rust, React-like | | ||
| | **Gleam** | Backend services | Runs on BEAM or compiles to JS | | ||
| | **Bash/POSIX Shell** | Scripts, automation | Keep minimal | | ||
| | **JavaScript** | Only where AffineScript cannot | MCP protocol glue, Deno APIs | | ||
| | **JavaScript** | Only where AffineScript cannot | MCP protocol glue, Bun APIs | | ||
| | **Nickel** | Configuration language | For complex configs | | ||
| | **Guile Scheme** | State/meta files | .machine_readable/6a2/STATE.a2ml, .machine_readable/6a2/META.a2ml, .machine_readable/6a2/ECOSYSTEM.a2ml | | ||
| | **Julia** | Batch scripts, data processing | Per RSR | | ||
|
|
@@ -38,10 +38,10 @@ The following files in `.machine_readable/` contain structured project metadata: | |
| | Banned | Replacement | | ||
| |--------|-------------| | ||
| | TypeScript | AffineScript | | ||
| | Node.js | Deno | | ||
| | npm | Deno | | ||
| | Bun | Deno | | ||
| | pnpm/yarn | Deno | | ||
| | Deno | Bun | | ||
| | Node.js | Bun | | ||
| | npm | Bun | | ||
| | pnpm/yarn | Bun | | ||
| | Go | Rust | | ||
| | Python | Julia/Rust/ReScript | | ||
| | Java/Kotlin | Rust/Tauri/Dioxus | | ||
|
|
@@ -61,8 +61,8 @@ Both are FOSS with independent governance (no Big Tech). | |
| ### Enforcement Rules | ||
|
|
||
| 1. **No new TypeScript files** - Convert existing TS to AffineScript | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 MEDIUM RISK The implementation does not reflect the description's claim of updating Rule 1 to mention ReScript. It currently still refers to TypeScript. |
||
| 2. **No package.json for runtime deps** - Use deno.json imports | ||
| 3. **No node_modules in production** - Deno caches deps automatically | ||
| 2. **Use `package.json` + `bun.lock` for JS runtime deps** - Bun is npm-compatible; a manifest is REQUIRED | ||
| 3. **`bun install --production` for production deps** - resolved from `package.json`, pinned via `bun.lock` | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win 🔎 Supported by static analysis🏁 Script executed: printf '%s\n' '--- repository conventions ---'
find /tmp/coderabbit-repo-knowledge/hyperpolymath-resource-record-fluctuator-f831bb14 -mindepth 2 -maxdepth 2 -type f -name '*.md' -print
printf '%s\n' '--- changed file diff ---'
git diff -- .claude/CLAUDE.md
printf '%s\n' '--- relevant file context ---'
cat -n .claude/CLAUDE.md | sed -n '1,130p'Repository: hyperpolymath/resource-record-fluctuator Length of output: 4425 🏁 Script executed: printf '%s\n' '--- scoped convention: repository root ---'
cat /tmp/coderabbit-repo-knowledge/hyperpolymath-resource-record-fluctuator-f831bb14/conventions/hinfo-loc-fluctuator-ada.md
printf '%s\n' '--- scoped convention: src ---'
cat /tmp/coderabbit-repo-knowledge/hyperpolymath-resource-record-fluctuator-f831bb14/conventions/hinfo-loc-fluctuator-ada-src.md
printf '%s\n' '--- Bun references in repository ---'
rg -n -C 3 'bun install|bun prune|production|devDependencies' --glob '!node_modules' --glob '!dist' --glob '!build' .Repository: hyperpolymath/resource-record-fluctuator Length of output: 33810 🌐 Web query:
💡 Result: To manage production dependencies in Bun, it is important to understand the distinct roles of bun install --production and bun prune --production. 1. bun install --production: This command installs only production dependencies from your package.json, excluding devDependencies [1][2]. Importantly, if devDependencies are already present in your node_modules directory (from a previous installation), this command will not remove them [1][3]. It simply ensures that no new devDependencies are added to the directory [1]. 2. bun prune --production: This command is specifically designed to clean up your node_modules directory [4]. It removes any packages that would not be installed in a production environment, such as devDependencies [4]. This combination is commonly used in workflows like Docker builds, where you may need devDependencies to perform a build step but want to exclude them from the final production image [4]. A standard pattern is as follows: 1. Install all dependencies (including devDependencies) to perform the build: bun install [4]. 2. Run your build process: bun run build [4]. 3. Remove the unnecessary devDependencies: bun prune --production [4]. In summary, use bun install --production when you want to start a fresh, production-only dependency install [3]. Use bun prune --production if you have already installed all dependencies and need to remove the devDependencies from an existing node_modules folder [1][4]. Citations:
Clarify the production install contract. If this rule must produce production-only artefacts, require a clean install or 🤖 Prompt for AI Agents |
||
| 4. **No Go code** - Use Rust instead | ||
| 5. **No Python anywhere** - Use Julia for data/batch, Rust for systems, AffineScript for apps | ||
| 6. **No Kotlin/Swift for mobile** - Use Tauri 2.0+ or Dioxus | ||
|
|
@@ -71,7 +71,7 @@ Both are FOSS with independent governance (no Big Tech). | |
|
|
||
| - **Primary**: Guix (guix.scm) | ||
| - **Fallback**: Nix (flake.nix) | ||
| - **JS deps**: Deno (deno.json imports) | ||
| - **JS deps**: Bun (`package.json` + `bun.lock`). Declare tooling as a devDependency and run `bunx --no-install --bun <tool>` — a bare `bunx <tool>` can fetch an unpinned package and may start Node via its shebang. | ||
|
|
||
| ### Security Requirements | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 MEDIUM RISK
Suggestion: To ensure AI agents strictly follow the new runtime policy, Deno should be added to the BANNED table with Bun as the recommended replacement.