docs: fix install command

twlite · twlite · commit 4bccce02f87e · 2026-03-02T16:55:08.000+05:45
diff --git a/apps/website/docs/guide/05-official-plugins/01-commandkit-ai.mdx b/apps/website/docs/guide/05-official-plugins/01-commandkit-ai.mdx
@@ -41,7 +41,7 @@ language models.
 Install the plugin and your preferred AI SDK:
 
 ```bash npm2yarn
-npm install @commandkit/ai@next
+npm install @commandkit/ai
 ```
 
 You also need to install the AI SDK for the model you want to use. For
@@ -67,17 +67,21 @@ export default defineConfig({
 });
 ```
 
-Then create an AI configuration file to set up your AI model. This can be done in two ways, one via CLI and another manually.
+Then create an AI configuration file to set up your AI model. This can
+be done in two ways, one via CLI and another manually.
 
 ### With CLI
 
-Use the following command to automatically generate `ai.ts` (or js) file in the project:
+Use the following command to automatically generate `ai.ts` (or js)
+file in the project:
 
 ```sh
 commandkit create ai
 ```
 
-This command creates `ai.ts` (or js) file inside the `src` directory with openai o3-mini model. You can change it to any other supported models if needed.
+This command creates `ai.ts` (or js) file inside the `src` directory
+with openai o3-mini model. You can change it to any other supported
+models if needed.
 
 ### Manual
 
@@ -274,9 +278,10 @@ configureAI({
 
 ### Selectively enabling built-in tools
 
-In many cases, you may not need all built-in tools. You can selectively enable
-specific tools by disabling built-in tools and then manually adding only the
-ones you need using the exported `defaultTools` record:
+In many cases, you may not need all built-in tools. You can
+selectively enable specific tools by disabling built-in tools and then
+manually adding only the ones you need using the exported
+`defaultTools` record:
 
 ```ts title="src/ai.ts"
 import { createGoogleGenerativeAI } from '@ai-sdk/google';
@@ -309,8 +314,9 @@ configureAI({
 });
 ```
 
-This approach gives you full control over which built-in tools are available to
-the AI, making your implementation cleaner and more intentional.
+This approach gives you full control over which built-in tools are
+available to the AI, making your implementation cleaner and more
+intentional.
 
 ## Creating custom tools
 
diff --git a/apps/website/docs/guide/05-official-plugins/02-commandkit-analytics.mdx b/apps/website/docs/guide/05-official-plugins/02-commandkit-analytics.mdx
@@ -13,7 +13,7 @@ data itself.
 Install the analytics package to get started:
 
 ```bash npm2yarn
-npm install @commandkit/analytics@next
+npm install @commandkit/analytics
 ```
 
 ## How it works
diff --git a/apps/website/docs/guide/05-official-plugins/03-commandkit-cache.mdx b/apps/website/docs/guide/05-official-plugins/03-commandkit-cache.mdx
@@ -13,7 +13,7 @@ improving response times and reducing external service usage.
 Install the cache package to get started:
 
 ```bash npm2yarn
-npm install @commandkit/cache@next
+npm install @commandkit/cache
 ```
 
 ## Setup
diff --git a/apps/website/docs/guide/05-official-plugins/04-commandkit-devtools.mdx b/apps/website/docs/guide/05-official-plugins/04-commandkit-devtools.mdx
@@ -33,7 +33,7 @@ only. Features and APIs may change in future releases.
 Install the devtools plugin using your preferred package manager:
 
 ```sh npm2yarn
-npm install @commandkit/devtools@next
+npm install @commandkit/devtools
 ```
 
 ## Setup
diff --git a/apps/website/docs/guide/05-official-plugins/05-commandkit-i18n.mdx b/apps/website/docs/guide/05-official-plugins/05-commandkit-i18n.mdx
@@ -28,7 +28,7 @@ interactions.
 ## Installation
 
 ```sh npm2yarn
-npm install @commandkit/i18n@next
+npm install @commandkit/i18n
 ```
 
 ## Basic setup
diff --git a/apps/website/docs/guide/05-official-plugins/06-commandkit-legacy.mdx b/apps/website/docs/guide/05-official-plugins/06-commandkit-legacy.mdx
@@ -19,7 +19,7 @@ major changes to your existing code.
 ## Installation
 
 ```sh npm2yarn
-npm install @commandkit/legacy@next
+npm install @commandkit/legacy
 ```
 
 ## Usage
diff --git a/apps/website/docs/guide/05-official-plugins/08-commandkit-tasks.mdx b/apps/website/docs/guide/05-official-plugins/08-commandkit-tasks.mdx
@@ -10,7 +10,7 @@ cleanup, the tasks plugin has you covered.
 ## Installation
 
 ```bash
-npm install @commandkit/tasks@next
+npm install @commandkit/tasks
 ```
 
 ## Basic setup
@@ -160,11 +160,10 @@ export default defineConfig({
 });
 ```
 
-:::warning
-Avoid loading the code that keeps the event loop alive inside the build process.
-Otherwise the build command will never exit. Use the helper functions such as `buildOnly()` or `noBuildOnly()`
-to conditionally load the code in appropriate places.
-:::
+:::warning Avoid loading the code that keeps the event loop alive
+inside the build process. Otherwise the build command will never exit.
+Use the helper functions such as `buildOnly()` or `noBuildOnly()` to
+conditionally load the code in appropriate places. :::
 
 ## Creating your first task
 
diff --git a/apps/website/docs/guide/05-official-plugins/09-commandkit-queue.mdx b/apps/website/docs/guide/05-official-plugins/09-commandkit-queue.mdx
@@ -19,13 +19,13 @@ multiple services using a simple, unified interface.
 ## Installation
 
 ```bash
-npm install @commandkit/queue@next
+npm install @commandkit/queue
 ```
 
 For Discord.js integration with Redis:
 
 ```bash
-npm install @commandkit/queue@next @discordjs/brokers ioredis
+npm install @commandkit/queue @discordjs/brokers ioredis
 ```
 
 ## Basic setup
diff --git a/apps/website/docs/guide/08-advanced/01-setup-commandkit-manually.mdx b/apps/website/docs/guide/08-advanced/01-setup-commandkit-manually.mdx
@@ -16,7 +16,7 @@ manually into your application.
 To install CommandKit, you can use the following command:
 
 ```sh npm2yarn
-npm install commandkit@next
+npm install commandkit
 ```
 
 ## Configuration file
diff --git a/apps/website/docs/guide/08-advanced/04-migrating-from-v0.mdx b/apps/website/docs/guide/08-advanced/04-migrating-from-v0.mdx
@@ -36,7 +36,7 @@ enhanced developer experience features.
 Begin your migration by updating to the latest version of CommandKit:
 
 ```bash npm2yarn
-npm install commandkit@next
+npm install commandkit
 ```
 
 This command will install CommandKit v1 and update your `package.json`
diff --git a/apps/website/docs/guide/08-advanced/05-using-cli-api.mdx b/apps/website/docs/guide/08-advanced/05-using-cli-api.mdx
@@ -6,27 +6,34 @@ description: Learn how to use the CommandKit CLI API for advanced use cases
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-The `commandkit/cli` module provides programmatic access to CommandKit's CLI functionality. This API is **not recommended for normal use cases** but can be useful in specific situations where you need to integrate CommandKit's build and development processes into custom tooling or scripts.
+The `commandkit/cli` module provides programmatic access to
+CommandKit's CLI functionality. This API is **not recommended for
+normal use cases** but can be useful in specific situations where you
+need to integrate CommandKit's build and development processes into
+custom tooling or scripts.
 
-:::warning Advanced Usage Only
-This API is intended for advanced users who need to integrate CommandKit into custom build systems or development workflows. For most users, the standard CLI commands (`commandkit dev`, `commandkit build`, etc.) should be sufficient.
-:::
+:::warning Advanced Usage Only This API is intended for advanced users
+who need to integrate CommandKit into custom build systems or
+development workflows. For most users, the standard CLI commands
+(`commandkit dev`, `commandkit build`, etc.) should be sufficient. :::
 
 ## Installation
 
 The CLI API is available as part of the main CommandKit package:
 
 ```sh npm2yarn
-npm install commandkit@next
+npm install commandkit
 ```
 
 ## Available Modules
 
-The CLI API is organized into several modules, each providing specific functionality:
+The CLI API is organized into several modules, each providing specific
+functionality:
 
 ### Development Module
 
-The `development` module provides functions for running CommandKit in development mode with hot module reloading.
+The `development` module provides functions for running CommandKit in
+development mode with hot module reloading.
 
 ```ts
 import { development } from 'commandkit/cli';
@@ -43,7 +50,8 @@ const process = devServer.getProcess();
 
 **Key Functions:**
 
-- `bootstrapDevelopmentServer(configPath?: string)` - Starts the development server with file watching and HMR
+- `bootstrapDevelopmentServer(configPath?: string)` - Starts the
+  development server with file watching and HMR
 
 ### Production Module
 
@@ -63,8 +71,10 @@ const server = await production.bootstrapProductionServer(
 
 **Key Functions:**
 
-- `createProductionBuild(configPath?: string)` - Creates an optimized production build
-- `bootstrapProductionServer(configPath?: string)` - Starts the production server
+- `createProductionBuild(configPath?: string)` - Creates an optimized
+  production build
+- `bootstrapProductionServer(configPath?: string)` - Starts the
+  production server
 
 ### Environment Module
 
@@ -85,8 +95,10 @@ env.setCLIEnv();
 
 **Key Functions:**
 
-- `DevEnv(static?: boolean)` - Returns development environment variables
-- `ProdEnv(static?: boolean)` - Returns production environment variables
+- `DevEnv(static?: boolean)` - Returns development environment
+  variables
+- `ProdEnv(static?: boolean)` - Returns production environment
+  variables
 - `setCLIEnv()` - Sets the CLI environment flag
 
 ### CLI Module
@@ -102,7 +114,8 @@ await cli.bootstrapCommandkitCLI(['dev', '--config', './custom.config.ts']);
 
 **Key Functions:**
 
-- `bootstrapCommandkitCLI(argv: string[], options?: ParseOptions)` - Bootstraps the CLI with custom arguments
+- `bootstrapCommandkitCLI(argv: string[], options?: ParseOptions)` -
+  Bootstraps the CLI with custom arguments
 
 ### Compiler Module
 
@@ -122,11 +135,13 @@ await compiler.buildApplication({
 
 **Key Functions:**
 
-- `buildApplication(options: ApplicationBuildOptions)` - Builds the application with custom options
+- `buildApplication(options: ApplicationBuildOptions)` - Builds the
+  application with custom options
 
 ### App Process Module
 
-The `appProcess` module manages child processes for running applications.
+The `appProcess` module manages child processes for running
+applications.
 
 ```ts
 import { appProcess } from 'commandkit/cli';
@@ -141,11 +156,13 @@ const process = appProcess.createAppProcess(
 
 **Key Functions:**
 
-- `createAppProcess(fileName: string, cwd: string, isDev: boolean)` - Creates a new application process
+- `createAppProcess(fileName: string, cwd: string, isDev: boolean)` -
+  Creates a new application process
 
 ### Type Checker Module
 
-The `typeChecker` module provides TypeScript type checking functionality.
+The `typeChecker` module provides TypeScript type checking
+functionality.
 
 ```ts
 import { typeChecker } from 'commandkit/cli';
@@ -156,11 +173,13 @@ await typeChecker.performTypeCheck('./src');
 
 **Key Functions:**
 
-- `performTypeCheck(path: string)` - Performs TypeScript type checking on the specified path
+- `performTypeCheck(path: string)` - Performs TypeScript type checking
+  on the specified path
 
 ### Utilities Module
 
-The `utilities` module provides common utility functions used throughout the CLI.
+The `utilities` module provides common utility functions used
+throughout the CLI.
 
 ```ts
 import { utilities } from 'commandkit/cli';
@@ -177,15 +196,19 @@ utilities.panic('Something went wrong!');
 
 **Key Functions:**
 
-- `findEntrypoint(dir: string)` - Finds the entrypoint file in a directory
+- `findEntrypoint(dir: string)` - Finds the entrypoint file in a
+  directory
 - `write(message: any)` - Writes a message to stdout
 - `panic(message: any)` - Exits the process with an error message
-- `loadTypeScript(errorMessage?: string)` - Loads TypeScript dynamically
-- `loadConfigFileFromPath(target: string)` - Loads configuration from a specific path
+- `loadTypeScript(errorMessage?: string)` - Loads TypeScript
+  dynamically
+- `loadConfigFileFromPath(target: string)` - Loads configuration from
+  a specific path
 
 ## Example: Custom Build Script
 
-Here's an example of how you might use the CLI API to create a custom build script:
+Here's an example of how you might use the CLI API to create a custom
+build script:
 
 ```ts
 import { production, compiler, typeChecker } from 'commandkit/cli';
@@ -213,7 +236,8 @@ customBuild();
 
 ## Example: Custom Development Server
 
-Here's an example of creating a custom development server with additional functionality:
+Here's an example of creating a custom development server with
+additional functionality:
 
 ```ts
 import { development, env } from 'commandkit/cli';
@@ -244,15 +268,23 @@ customDevServer();
 
 ## Important Notes
 
-1. **Internal API**: These functions are marked as `@private` and `@internal`, meaning they may change without notice in future versions.
+1. **Internal API**: These functions are marked as `@private` and
+   `@internal`, meaning they may change without notice in future
+   versions.
 
-2. **Error Handling**: Always wrap CLI API calls in try-catch blocks as they may throw errors.
+2. **Error Handling**: Always wrap CLI API calls in try-catch blocks
+   as they may throw errors.
 
-3. **Process Management**: When using `createAppProcess`, make sure to properly manage the returned child process.
+3. **Process Management**: When using `createAppProcess`, make sure to
+   properly manage the returned child process.
 
-4. **Configuration**: Most functions accept an optional `configPath` parameter. If not provided, they will look for configuration files in the current working directory.
+4. **Configuration**: Most functions accept an optional `configPath`
+   parameter. If not provided, they will look for configuration files
+   in the current working directory.
 
-5. **Environment Variables**: The environment modules provide pre-configured environment variables for development and production modes.
+5. **Environment Variables**: The environment modules provide
+   pre-configured environment variables for development and production
+   modes.
 
 ## When to Use the CLI API
 
@@ -261,7 +293,9 @@ Consider using the CLI API when you need to:
 - Integrate CommandKit into existing build systems
 - Create custom development workflows
 - Build tooling that wraps CommandKit functionality
-- Implement custom file watching or hot reloading (though we recommend using the plugins api for this)
+- Implement custom file watching or hot reloading (though we recommend
+  using the plugins api for this)
 - Create automated deployment scripts
 
-For most use cases, the standard CLI commands should be sufficient and are the recommended approach.
+For most use cases, the standard CLI commands should be sufficient and
+are the recommended approach.
diff --git a/apps/website/src/components/home/GetStartedSection.tsx b/apps/website/src/components/home/GetStartedSection.tsx
@@ -23,9 +23,7 @@ export default function GetStartedSection(): React.JSX.Element {
             <div className="font-mono text-white">
               <div className="flex gap-1">
                 <span className="text-gray-400">$</span>
-                <span className="text-cyan-300">
-                  npm create commandkit@next
-                </span>
+                <span className="text-cyan-300">npm create commandkit</span>
               </div>
               <div className="text-gray-400 mt-2">
                 # Follow the interactive setup
