fix: windows issues

Author: ImGajeed76

build.ts

@@ -106,13 +106,44 @@ async function typeCheck() {
 async function buildCLI() {
     logger.start("Compiling CLI with bun...");
 
+    const externalDependencies = [
+        // Node.js built-ins
+        "fs",
+        "path",
+        "os",
+        "util",
+        "events",
+        "stream",
+        "buffer",
+        "crypto",
+        // Problematic packages that cause editions-autoloader errors
+        "version-compare",
+        "editions",
+        "errlop",
+        "istextorbinary",
+        // Large dependencies that should remain external
+        "typescript",
+        "commander",
+        "chalk",
+        "ansis",
+        // All npm dependencies (alternative approach)
+        ...Object.keys(packageJson.dependencies || {}),
+        ...Object.keys(packageJson.devDependencies || {}),
+    ];
+
     const result = await build({
         entrypoints: ["src/cli.ts"],
         outdir: "bin/build",
         target: "node",
         define: {
             __VERSION__: `"${version}"`,
         },
+        external: externalDependencies,
+        minify: false,
+        sourcemap: "none",
+        splitting: false,
+        format: "esm",
+        packages: "external",
     });
 
     if (result.success) {
@@ -302,10 +333,19 @@ async function createExecutable() {
     const executableContent = `#!/usr/bin/env node
 ${builtCode}`;
 
-    writeFileSync("bin/axogen", executableContent);
-    chmodSync("bin/axogen", "755");
+    // Create the main JavaScript executable
+    writeFileSync("bin/axogen.js", executableContent);
+    chmodSync("bin/axogen.js", "755");
+
+    // Create Windows batch launcher
+    const windowsLauncher = `@echo off
+rem Windows launcher for axogen
+node "%~dp0axogen.js" %*
+`;
+    writeFileSync("bin/axogen.cmd", windowsLauncher);
 
-    logger.file("Executable created", "bin/axogen");
+    logger.success("Executable created: bin/axogen.js");
+    logger.success("Windows launcher created: bin/axogen.cmd");
 }
 
 function cleanup() {

package.json

@@ -1,6 +1,6 @@
 {
     "name": "@axonotes/axogen",
-    "version": "0.5.1",
+    "version": "0.5.5",
     "description": "TypeScript-native configuration system that unifies typed environment variables, code generation, and task management for any project",
     "type": "module",
     "main": "dist/index.cjs",
@@ -19,17 +19,18 @@
         }
     },
     "bin": {
-        "axogen": "./bin/axogen"
+        "axogen": "./bin/axogen.js"
     },
     "files": [
-        "bin",
+        "bin/axogen.js",
+        "bin/axogen.cmd",
         "dist"
     ],
     "scripts": {
         "build": "bun run build.ts",
         "preview": "bun run format && bun test && bun run build && bun link",
         "pub": "bun run format && bun test && bun run build && bun publish",
-        "test:local": "bun run build && ./bin/axogen --version",
+        "test:local": "bun run build && ./bin/axogen.js --version",
         "docs:start": "cd website && bun run start",
         "docs:build": "cd website && bun run build",
         "docs:serve": "cd website && bun run serve",

website/docs/09-windows.md

@@ -0,0 +1,28 @@
+---
+title: Windows
+description: How to use Axogen on Windows
+keywords: [advanced axogen, windows configuration, axogen windows setup]
+sidebar_position: 9
+---
+
+# Windows
+
+Sadly, Windows is not a first-class citizen in the Axogen world. But you can
+still use it with some workarounds.
+
+## Using Axogen on Windows
+
+On Linux and macOS, you would run Axogen like this:
+
+```bash
+axogen generate
+```
+
+On Windows, you need to use `npx` (or your package manager's equivalent):
+
+```bash npm2yarn
+npx @axonotes/axogen generate
+```
+
+This is the same for all commands. Just prepend `npx @axonotes/axogen` to the
+command you want to run instead of `axogen`.