tkeron 5.0.0 → 5.0.1

package/README.md

@@ -82,8 +82,8 @@ document.getElementById("quote").textContent = data.content;
 
 ```bash
 tk init <name>           # Initialize new project
-tk build [src] [out]     # Build project (default: websrc → web)
-tk dev [src] [out]       # Dev server with hot reload (port 3000)
+tk build                 # Build project (websrc → web)
+tk dev [port] [host]     # Dev server with hot reload (default: localhost:3000)
 ```
 
 **Aliases:** `tk i`, `tk b`, `tk d`

package/changelog.md

@@ -1,3 +1,21 @@
+# v5.0.1
+
+## Documentation fixes and dependency updates
+
+- Fix: `tk build` and `tk dev` CLI signatures corrected in README (removed wrong `[src] [out]` args, aligned with v5.0 breaking change)
+- Fix: Component resolution docs updated to reflect actual glob search behavior (not limited to root `websrc/`)
+- Fix: Build process docs updated to include `.com.md` processing step and iterative loop (up to 10 iterations)
+- Fix: `tsconfig.json` example corrected to match real config (`lib: ["ESNext", "DOM"]`, removed `types: ["bun-types"]`)
+- Fix: TypeScript compilation docs clarified — Bun transpiler does NOT type-check, only transpiles
+- Fix: Broken link `tkeron.dev/docs` → `tkeron.com`
+- Fix: `components-html.md` quick start used `<button>` (reserved HTML tag, no hyphen) — replaced with `<my-button>`
+- Fix: `best-practices.md` Summary had orphaned/corrupted code fragment — removed
+- Fix: Added `.com.md` to all feature lists, tables, and build process diagrams across all docs
+- Fix: `package.json` description updated to reflect actual purpose
+- Deps: `bun update --latest` — updated all dependencies
+
+---
+
 # v5.0.0
 
 ## Breaking: sourceDir and targetDir removed as CLI arguments

package/docs/best-practices.md

@@ -231,23 +231,20 @@ document.getElementById("stars").textContent = data.public_repos;
 
 - HTML components: static markup
 - TypeScript components: dynamic generation
+- Markdown components: content in Markdown
 - Pre-rendering: DOM manipulation at build time
 - Browser code: regular TypeScript/JavaScript
 - No bundling of npm packages
 - No type checking (use `tsc --noEmit`)
 - Powered by Bun
-  document.querySelectorAll('.my-button').forEach(btn => {
-  btn.addEventListener('click', handleClick);
-  });
-  });
 
-````
+---
 
 ```typescript
 // ❌ Don't try to maintain state
 let count = 0; // This is meaningless
 com.innerHTML = `<button>Count: ${count}</button>`;
-````
+```
 
 **Solution:** Use client-side JavaScript for stateful UI.
 

package/docs/cli-reference.md

@@ -75,16 +75,20 @@ tk b
 1. Creates temporary directory as sibling to source
 2. Copies source to temp directory
 3. Runs `.pre.ts` files (pre-rendering)
-4. Processes `.com.ts` components (TypeScript components)
-5. Processes `.com.html` components (HTML components)
-6. Compiles TypeScript to JavaScript
-7. Copies result to target directory
-8. Cleans up temporary directory
+4. Iterative component processing (up to 10 iterations):
+   - Processes `.com.ts` components (TypeScript components)
+   - Processes `.com.html` components (HTML components)
+   - Processes `.com.md` components (Markdown components)
+   - Repeats until no changes are detected
+5. Compiles TypeScript to JavaScript
+6. Copies result to target directory
+7. Cleans up temporary directory
 
 **Files Excluded from Output:**
 
 - `*.com.html` - HTML components (inlined)
 - `*.com.ts` - TypeScript components (inlined)
+- `*.com.md` - Markdown components (inlined)
 - `*.pre.ts` - Pre-rendering scripts (executed)
 
 **Exit Codes:**
@@ -448,8 +452,8 @@ Tkeron doesn't require a `tsconfig.json`, but you can add one for editor support
   "compilerOptions": {
     "target": "ESNext",
     "module": "ESNext",
+    "lib": ["ESNext", "DOM"],
     "moduleResolution": "bundler",
-    "types": ["bun-types"],
     "strict": true,
     "skipLibCheck": true
   },
@@ -635,7 +639,7 @@ tk
 This document! Also available at:
 
 - [GitHub Repository](https://github.com/tkeron/tkeron)
-- [Documentation Site](https://tkeron.dev/docs)
+- [Documentation Site](https://tkeron.com)
 
 ### Report Issues
 

package/docs/common-issues.md

@@ -125,9 +125,9 @@ blog-post.com.ts      → <blog-post>
 
 ## TypeScript Compilation
 
-### Issue: TypeScript Errors Prevent Build
+### Issue: TypeScript Errors in Source
 
-**Problem:** Type errors block compilation
+**Problem:** TypeScript code has type errors
 
 ```typescript
 // ❌ WRONG
@@ -135,18 +135,24 @@ const user = { name: "Alice" };
 user.age = 30; // Error: Property 'age' does not exist
 ```
 
-**Why this happens:**
+**Why this matters:**
 
-- Tkeron uses Bun's TypeScript transpiler
-- Type errors can prevent successful builds
-- Missing types for global variables
+- Tkeron uses Bun's TypeScript transpiler, which **does NOT type-check** — it only transpiles
+- Type errors won't prevent the build from running
+- However, type errors may indicate real bugs in your code
+- Missing types for global variables can confuse your IDE
 
 **Solution:**
 
+- Run `tsc --noEmit` separately to catch type errors before building
 - Use `tkeron.d.ts` for global type declarations
-- Fix type errors before building
 - Use `any` strategically if types are complex
 
+```bash
+# Check types, then build
+tsc --noEmit && tk build
+```
+
 ```typescript
 // ✅ CORRECT
 const user: { name: string; age?: number } = { name: "Alice" };
@@ -166,16 +172,17 @@ user.age = 30; // OK
 
 **Why this happens:**
 
-- Tkeron searches in 2 locations only:
+- Tkeron searches in 2 ways:
   1. Same directory as HTML file
-  2. Root directory (`websrc/`)
-- Not in subdirectories or parent directories (except root)
+  2. Glob search across the entire source tree
+- If no match is found in either, the element remains unchanged
 
 **Solution:**
-Either place component:
+Place the component file anywhere in the source tree — Tkeron will find it via glob search. For clarity, common locations:
 
-- In `blog/user-card.com.html` (next to `post.html`)
-- Or in `websrc/user-card.com.html` (root, available everywhere)
+- In `blog/user-card.com.html` (next to `post.html` — higher priority)
+- In `websrc/user-card.com.html` (root)
+- In `websrc/components/user-card.com.html` (organized in a subfolder)
 
 ## Build Performance
 

package/docs/components-html.md

@@ -7,7 +7,7 @@ HTML components (`.com.html` files) are the simplest way to create reusable piec
 Create a file named with `.com.html` extension:
 
 ```html
-<!-- button.com.html -->
+<!-- my-button.com.html -->
 <button class="btn">Click me</button>
 ```
 
@@ -15,7 +15,7 @@ Use it with a matching custom element:
 
 ```html
 <!-- index.html -->
-<button></button>
+<my-button></my-button>
 ```
 
 Build, and the custom element is replaced with the component's content.
@@ -36,7 +36,7 @@ Component filenames must:
 | -------------------- | -------------- | ------------------------- |
 | `user-card.com.html` | `<user-card>`  | ✅ Yes                    |
 | `nav-menu.com.html`  | `<nav-menu>`   | ✅ Yes                    |
-| `header.com.html`    | `<header>`     | ❌ No (no hyphen)         |
+| `card.com.html`      | `<card>`       | ❌ No (no hyphen)         |
 | `UserCard.com.html`  | `<user-card>`  | ✅ Yes (case-insensitive) |
 
 ### 2. Component Resolution
@@ -44,23 +44,25 @@ Component filenames must:
 Tkeron looks for components in this order:
 
 1. **Same directory** as the file using it
-2. **Root directory** (`websrc/`)
+2. **Any directory** in the source tree (via glob search)
 
 **Example structure:**
 
 ```
 websrc/
 ├── index.html
-├── header.com.html          # Available to all files
+├── site-header.com.html        # Available to all files
+├── components/
+│   └── blog-comment.com.html   # Also available to all files
 ├── blog/
 │   ├── post.html
-│   └── comment.com.html     # Available only to blog/post.html
+│   └── blog-comment.com.html   # Takes priority for blog/post.html
 ```
 
 In `blog/post.html`:
 
-- `<comment>` → Finds `blog/comment.com.html` first
-- `<header>` → Falls back to `websrc/header.com.html`
+- `<blog-comment>` → Finds `blog/blog-comment.com.html` first (same directory)
+- `<site-header>` → Found via glob search in the source tree
 
 ### 3. Build Process
 

package/docs/components-markdown.md

@@ -50,23 +50,23 @@ Component filenames must:
 Tkeron looks for components in this order:
 
 1. **Same directory** as the file using it
-2. **Root directory** (`websrc/`)
+2. **Any directory** in the source tree (via glob search)
 
 **Example structure:**
 
 ```
 websrc/
 ├── index.html
-├── site-intro.com.md         # Available to all files
+├── site-intro.com.md           # Available to all files
 ├── blog/
 │   ├── post.html
-│   └── post-footer.com.md    # Available only to blog/post.html
+│   └── post-footer.com.md      # Takes priority for blog/post.html
 ```
 
 In `blog/post.html`:
 
-- `<post-footer>` → Finds `blog/post-footer.com.md` first
-- `<site-intro>` → Falls back to `websrc/site-intro.com.md`
+- `<post-footer>` → Finds `blog/post-footer.com.md` first (same directory)
+- `<site-intro>` → Found via glob search in the source tree
 
 ### 3. Component Priority
 

package/docs/components-typescript.md

@@ -84,7 +84,7 @@ Custom elements in HTML must contain at least one hyphen to distinguish them fro
 Same as HTML components:
 
 1. **Same directory** as the file using it
-2. **Root directory** (`websrc/`)
+2. **Any directory** in the source tree (via glob search)
 
 ### IDE Support & IntelliSense
 

package/docs/getting-started.md

@@ -88,7 +88,7 @@ web/
 └── ...              # Other processed files
 ```
 
-Notice that `.com.html`, `.com.ts`, and `.pre.ts` files are **not** copied to output - they're processed and inlined.
+Notice that `.com.html`, `.com.ts`, `.com.md`, and `.pre.ts` files are **not** copied to output - they're processed and inlined.
 
 ## Start Development Server
 
@@ -198,6 +198,7 @@ Open `web/index.html` in your browser. You'll see the greeting component inlined
 | `.ts` / `.js`       | Scripts for pages     | ✅ Yes (compiled) |
 | `.com.html`         | HTML components       | ❌ No (inlined)   |
 | `.com.ts`           | TypeScript components | ❌ No (inlined)   |
+| `.com.md`           | Markdown components   | ❌ No (inlined)   |
 | `.pre.ts`           | Pre-rendering scripts | ❌ No (executed)  |
 | `.css`              | Stylesheets           | ✅ Yes            |
 | Images, fonts, etc. | Static assets         | ✅ Yes            |
@@ -271,4 +272,4 @@ tk dev 3001
 
 - Component names **must** contain a hyphen: `user-card`, not `usercard`
 - File must be named exactly: `user-card.com.html`
-- Component files must be in `websrc/` or the same directory as the page using them
+- Component files can be anywhere in the source tree — Tkeron searches the same directory first, then the entire source via glob

package/docs/overview.md

@@ -11,6 +11,7 @@ Powered by [Bun](https://bun.sh).
 - Compiles TypeScript to JavaScript
 - Inlines HTML components (`.com.html`)
 - Executes TypeScript components (`.com.ts`) at build time
+- Renders Markdown components (`.com.md`) at build time
 - Runs pre-rendering scripts (`.pre.ts`)
 - Copies assets
 - Dev server with hot reload
@@ -107,11 +108,12 @@ websrc/               Build Steps           web/
 ├── index.html    →  1. .pre.ts        →  ├── index.html
 ├── index.ts         2. .com.ts           ├── index.js
 ├── index.pre.ts     3. .com.html
-├── nav.com.html     4. TypeScript
-└── card.com.ts      5. Assets
+├── nav.com.html     4. .com.md
+├── card.com.ts      5. TypeScript
+└── info.com.md      6. Assets
 ```
 
-Component files (`.com.html`, `.com.ts`, `.pre.ts`) are not copied to output.
+Component files (`.com.html`, `.com.ts`, `.com.md`, `.pre.ts`) are not copied to output.
 
 ---
 

package/docs/pre-rendering.md

@@ -71,10 +71,13 @@ This is the parsed DOM from the corresponding `.html` file.
 
 ```
 1. Run .pre.ts files    → Modify HTML documents
-2. Process .com.ts      → Replace TypeScript components
-3. Process .com.html    → Replace HTML components
-4. Compile .ts to .js   → TypeScript compilation
-5. Copy to output       → Final build
+2. Iterative component processing (up to 10 iterations):
+   a. Process .com.ts   → Replace TypeScript components
+   b. Process .com.html → Replace HTML components
+   c. Process .com.md   → Replace Markdown components
+   d. Repeat until no changes
+3. Compile .ts to .js   → TypeScript compilation
+4. Copy to output       → Final build
 ```
 
 Pre-rendering happens **first**, so you can inject components dynamically.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tkeron",
-  "version": "5.0.0",
-  "description": "CLI tool for backend-driven frontend development with TypeScript.",
+  "version": "5.0.1",
+  "description": "CLI build tool for vanilla web development with TypeScript.",
   "type": "module",
   "main": "./src/index.ts",
   "exports": {