Release v1.0.0

- Add standalone 'watch' command for continuous compilation
- Update all documentation for CLI command parity
- Update templates with TypeScript/SCSS, CDN, and areas sections
- Remove preview designation from version

Author: stef-k

README.md

@@ -20,7 +20,7 @@ It wraps `esbuild` behind a simple `.NET + YAML` workflow:
 
 This is for ASP.NET devs who want modern bundling without committing to the full Node toolchain.
 
-> **Status:** v1.0.0-preview.x - Core implementation complete. Production-ready for early adopters. Expect breaking changes until v1.0.
+> **Status:** v1.0 - Production-ready.
 
 ## Installation
 
@@ -37,7 +37,7 @@ This is the only package required for both **runtime** and **production builds**
 
 ### 2. Install the CLI tool (optional)
 
-The CLI provides commands for development compilation, production builds, and diagnostics (`dev`, `build`, `init`, `check`):
+The CLI provides commands for development compilation, production builds, and diagnostics (`dev`, `watch`, `build`, `init`, `check`):
 
 ```bash
 # Global install (available everywhere)
@@ -49,7 +49,7 @@ dotnet tool install MvcFrontendKit.Cli
 ```
 
 > **Note:** The CLI is **not required** for production builds. Production bundling is handled automatically by MSBuild targets during `dotnet publish -c Release`. However, the CLI is useful for:
-> - Development: Compile TypeScript/SCSS on-the-fly with `dotnet frontend dev`
+> - Development: Compile TypeScript/SCSS with `dotnet frontend dev` or `dotnet frontend watch`
 > - Standalone builds: Build bundles without running MSBuild with `dotnet frontend build` (useful for CDN workflows)
 > - Diagnostics: Validate configuration and assets with `dotnet frontend check`
 
@@ -111,7 +111,7 @@ Add helpers to your `_Layout.cshtml` or equivalent:
   dotnet frontend dev
 
   # Or watch for changes (recommended)
-  dotnet frontend dev --watch
+  dotnet frontend watch
   ```
   Then run your app with `dotnet run` or `dotnet watch run`.
 
@@ -330,14 +330,14 @@ global:
 
 ### Development Workflow
 
-For development, use the `dev` command to compile TypeScript and SCSS files:
+For development, use the `dev` or `watch` command to compile TypeScript and SCSS files:
 
 ```bash
 # One-time compilation
 dotnet frontend dev
 
 # Watch mode (recommended)
-dotnet frontend dev --watch
+dotnet frontend watch
 ```
 
 This compiles your source files to `.js` and `.css` next to the originals, which are then served by the development helpers with cache-busting.
@@ -428,9 +428,12 @@ dotnet frontend init --force    # Overwrite existing
 
 # Compile TypeScript/SCSS for development
 dotnet frontend dev             # One-time compilation
-dotnet frontend dev --watch     # Watch mode with auto-recompile
 dotnet frontend dev --verbose   # Show detailed output
 
+# Watch for changes and recompile
+dotnet frontend watch           # Continuous watch mode
+dotnet frontend watch --verbose # Show detailed output
+
 # Validate configuration and assets
 dotnet frontend check           # Basic check
 dotnet frontend check --verbose # Detailed output
@@ -445,15 +448,12 @@ dotnet frontend build --verbose # Show detailed build output
 
 ### Development Compilation (`dev`)
 
-The `dev` command compiles TypeScript and SCSS files to JavaScript and CSS for development. This enables you to use TypeScript and SCSS without running production builds during development.
+The `dev` command compiles TypeScript and SCSS files to JavaScript and CSS for development (one-time).
 
 ```bash
 # Compile all TypeScript/SCSS files from frontend.config.yaml
 dotnet frontend dev
 
-# Watch for changes and recompile automatically
-dotnet frontend dev --watch
-
 # Show compilation details
 dotnet frontend dev --verbose
 ```
@@ -465,10 +465,18 @@ dotnet frontend dev --verbose
 - Output files are placed next to source files (e.g., `site.ts` → `site.js`)
 - Source maps are generated for debugging
 
-**Watch mode:**
+### Watch Mode (`watch`)
+
+The `watch` command compiles and then monitors for changes:
+
 ```bash
-dotnet frontend dev --watch
+# Start watching for changes
+dotnet frontend watch
+
+# With detailed output
+dotnet frontend watch --verbose
 ```
+
 - Monitors your `jsRoot` and `cssRoot` directories for changes
 - Automatically recompiles when `.ts`, `.tsx`, `.scss`, or `.sass` files change
 - Shows compilation results in real-time
@@ -480,12 +488,12 @@ dotnet frontend dev --watch
 dotnet watch run
 
 # Terminal 2: Watch and compile frontend assets
-dotnet frontend dev --watch
+dotnet frontend watch
 ```
 
 This gives you:
 - Hot reload for C# code (via `dotnet watch`)
-- Auto-compilation for TypeScript/SCSS (via `frontend dev --watch`)
+- Auto-compilation for TypeScript/SCSS (via `frontend watch`)
 - Browser refresh to see changes
 
 ### View Diagnostics (`--view` and `--all`)

SPEC.md

@@ -22,10 +22,10 @@ A small, .NET-native helper tool named **MvcFrontendKit** that:
 - Adds **components** as reusable JS/CSS units for partials, with runtime deduplication.
 - Plays nicely with `dotnet run` / `dotnet watch` without introducing HMR or SPA-level complexity.
 
-Out of scope (for this version):
+Out of scope:
 
 - Full SPA-style integration for Vue/React (dev servers, HMR).
-- CDN base URL for manifest URLs (implemented), SRI hashes and advanced incremental build caching (reserved as future extensions).
+- SRI hashes and advanced incremental build caching (reserved as future extensions).
 
 ### 1.1 Preprocessor Support (TypeScript & SCSS)
 
@@ -105,8 +105,11 @@ This is a zero-config feature:
      - Subsequent calls to `FrontendInclude("...")` for the same component emit nothing.
 
 5. **CLI helper** (optional but recommended)
-   - `dotnet frontend init`
-   - `dotnet frontend check [--verbose]`
+   - `dotnet frontend init` — scaffold configuration
+   - `dotnet frontend check [--verbose]` — validate config and assets
+   - `dotnet frontend dev [--verbose]` — compile TS/SCSS for development (one-time)
+   - `dotnet frontend watch [--verbose]` — compile and watch for changes
+   - `dotnet frontend build [--dry-run] [--verbose]` — production build (standalone)
 
 > **No HMR**
 > This tool does not provide hot module replacement. JS/CSS changes require a normal browser refresh. It is compatible with `dotnet watch` for Razor recompilation, but does not hook into ASP.NET hot reload semantics.
@@ -774,14 +777,41 @@ This helper is optional and intended for development troubleshooting. It can saf
   - `global.js` / `global.css` paths.
   - `views.overrides[*].js` / `css` paths.
   - `components[*].js` / `css` paths.
+  - `areas[*].js` / `css` paths.
 - Checks CSS files in bundling scope:
   - Warns or errors on disallowed `../` URLs based on `cssUrlPolicy`.
 - With `--verbose`, additionally:
   - Prints mapping of view keys to Dev assets and Prod bundle keys.
   - Prints component graph (including `depends`) and warns about cycles.
-  - May optionally inspect esbuild’s module graph to warn about circular JS imports (while still allowing them).
+  - Displays CDN and areas configuration.
+  - May optionally inspect esbuild's module graph to warn about circular JS imports (while still allowing them).
   - Optionally warns if any predicted bundle exceeds a configurable size threshold (e.g., 500KB).
 
+### 10.3 `dotnet frontend dev [--verbose]`
+
+- Compiles TypeScript and SCSS files to JavaScript and CSS for development.
+- Reads `frontend.config.yaml` to find all TypeScript (`.ts`, `.tsx`) and SCSS (`.scss`, `.sass`) files.
+- Compiles TypeScript using esbuild's native TypeScript loader.
+- Compiles SCSS using the bundled Dart Sass compiler.
+- Output files are placed next to source files (e.g., `site.ts` → `site.js`).
+- Source maps are generated for debugging.
+- With `--verbose`, shows detailed compilation output for each file.
+
+### 10.4 `dotnet frontend watch [--verbose]`
+
+- Same as `dev`, but continues running and monitors for changes.
+- Watches `jsRoot` and `cssRoot` directories for file changes.
+- Automatically recompiles when `.ts`, `.tsx`, `.scss`, or `.sass` files are modified.
+- Shows compilation results in real-time.
+- Press `Ctrl+C` to stop watching.
+
+### 10.5 `dotnet frontend build [--dry-run] [--verbose]`
+
+- Performs a production build identical to what MSBuild targets do during `dotnet publish -c Release`.
+- Useful for CDN workflows where bundles need to be generated independently of the publish process.
+- With `--dry-run`, previews bundles without writing files.
+- With `--verbose`, shows detailed build output including bundle sizes.
+
 ---
 
 ## 11. Migration Guidance (summary)
@@ -853,7 +883,10 @@ The tool ships from v1 as two NuGet packages:
    - Strongly recommended for development and CI workflows.
    - Exposes the `frontend` command:
      - `dotnet frontend init` — scaffold a fully commented `frontend.config.yaml`.
-     - `dotnet frontend check [--verbose]` — validate config, discover assets, and report problems before a build/publish.
+     - `dotnet frontend check [--verbose]` — validate config, discover assets, and report problems.
+     - `dotnet frontend dev [--verbose]` — compile TypeScript/SCSS for development.
+     - `dotnet frontend watch [--verbose]` — compile and watch for changes.
+     - `dotnet frontend build [--dry-run] [--verbose]` — production build (standalone).
    - Shares the same core parsing / validation logic as the library (via a shared project or internal package) so semantics stay in sync.
 
 Versioning & compatibility:

src/MvcFrontendKit.Cli/MvcFrontendKit.Cli.csproj

@@ -7,7 +7,7 @@
     <Nullable>enable</Nullable>
     <PackAsTool>true</PackAsTool>
     <ToolCommandName>dotnet-frontend</ToolCommandName>
-    <Version>1.0.0-preview.29</Version>
+    <Version>1.0.0</Version>
     <Authors>stef-k</Authors>
     <Description>CLI tool for MvcFrontendKit - compile TypeScript/SCSS during development, validate config and check assets. Uses esbuild and Dart Sass.</Description>
     <PackageTags>aspnetcore;mvc;razor;bundling;esbuild;sass;scss;typescript;frontend;cli</PackageTags>

src/MvcFrontendKit.Cli/Program.cs

@@ -20,6 +20,7 @@ static int Main(string[] args)
             "check" => HandleCheckCommand(args),
             "build" => HandleBuildCommand(args),
             "dev" => HandleDevCommand(args),
+            "watch" => HandleWatchCommand(args),
             "help" or "--help" or "-h" => ShowHelp(),
             "version" or "--version" or "-v" => ShowVersion(),
             _ => UnknownCommand(command)
@@ -34,6 +35,12 @@ static int HandleDevCommand(string[] args)
         return DevCommand.Execute(verbose, watch);
     }
 
+    static int HandleWatchCommand(string[] args)
+    {
+        var verbose = args.Contains("--verbose") || args.Contains("-v");
+        return DevCommand.Execute(verbose, watch: true);
+    }
+
     static int HandleCheckCommand(string[] args)
     {
         var verbose = args.Contains("--verbose") || args.Contains("-v");
@@ -68,7 +75,8 @@ static void PrintUsage()
         Console.WriteLine("Commands:");
         Console.WriteLine("  init            Create frontend.config.yaml with default settings");
         Console.WriteLine("  check           Validate config and check if assets exist");
-        Console.WriteLine("  dev             Compile TypeScript/SCSS for development");
+        Console.WriteLine("  dev             Compile TypeScript/SCSS for development (once)");
+        Console.WriteLine("  watch           Compile and watch for changes");
         Console.WriteLine("  build           Build frontend bundles (production)");
         Console.WriteLine("  help            Show this help message");
         Console.WriteLine("  version         Show version information");
@@ -96,10 +104,15 @@ static int ShowHelp()
         Console.WriteLine("    --skip-imports  Skip import path validation");
         Console.WriteLine();
         Console.WriteLine("  dev [options]");
-        Console.WriteLine("    Compile TypeScript and SCSS files for development.");
+        Console.WriteLine("    Compile TypeScript and SCSS files for development (one-time).");
         Console.WriteLine("    Creates .js files alongside .ts files, and .css files alongside .scss files.");
         Console.WriteLine("    --verbose     Show detailed compilation output");
         Console.WriteLine();
+        Console.WriteLine("  watch [options]");
+        Console.WriteLine("    Compile and watch for changes (continuous).");
+        Console.WriteLine("    Same as 'dev' but keeps running and recompiles on file changes.");
+        Console.WriteLine("    --verbose     Show detailed compilation output");
+        Console.WriteLine();
         Console.WriteLine("  build [options]");
         Console.WriteLine("    Build frontend bundles (same as 'dotnet publish -c Release' but standalone).");
         Console.WriteLine("    Useful for CDN workflows where you need bundles before deploying.");
@@ -108,9 +121,9 @@ static int ShowHelp()
         Console.WriteLine();
         Console.WriteLine("Workflow:");
         Console.WriteLine("  Development:");
-        Console.WriteLine("    1. Run 'dotnet frontend dev' to compile TS/SCSS to JS/CSS");
-        Console.WriteLine("    2. Run 'dotnet run' to start your app (serves raw JS/CSS files)");
-        Console.WriteLine("    3. After changes, re-run 'dotnet frontend dev'");
+        Console.WriteLine("    1. Run 'dotnet frontend watch' to compile and watch for changes");
+        Console.WriteLine("    2. In another terminal, run 'dotnet run' to start your app");
+        Console.WriteLine("    Or use 'dotnet frontend dev' for one-time compilation");
         Console.WriteLine();
         Console.WriteLine("  Production:");
         Console.WriteLine("    Run 'dotnet publish -c Release' which automatically:");
@@ -122,7 +135,7 @@ static int ShowHelp()
         Console.WriteLine("Examples:");
         Console.WriteLine("  dotnet frontend init");
         Console.WriteLine("  dotnet frontend dev");
-        Console.WriteLine("  dotnet frontend dev --verbose");
+        Console.WriteLine("  dotnet frontend watch");
         Console.WriteLine("  dotnet frontend check --all");
         Console.WriteLine("  dotnet frontend build --dry-run");
         return 0;

src/MvcFrontendKit.Cli/Templates/frontend.config.template.yaml

@@ -11,9 +11,9 @@ configVersion: 1
 # Just use .ts/.scss extensions in your file paths below - no config needed!
 #
 # CLI Commands:
-#   dotnet frontend dev    - One-time compile of TS/SCSS for development
+#   dotnet frontend dev    - Compile TS/SCSS for development (once)
+#   dotnet frontend watch  - Compile and watch for changes
 #   dotnet frontend build  - Production build with bundling and hashing
-#   dotnet frontend watch  - Watch mode for continuous compilation
 #   dotnet frontend check  - Validate configuration and assets
 # ============================================================================
 

src/MvcFrontendKit/MvcFrontendKit.csproj

@@ -4,7 +4,7 @@
     <TargetFramework>net10.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
-    <Version>1.0.0-preview.29</Version>
+    <Version>1.0.0</Version>
     <Authors>stef-k</Authors>
     <Description>Node-free frontend bundling toolkit for ASP.NET Core MVC / Razor applications. Uses esbuild for JS/TS bundling and Dart Sass for SCSS compilation.</Description>
     <PackageTags>aspnetcore;mvc;razor;bundling;esbuild;sass;scss;typescript;frontend</PackageTags>

src/MvcFrontendKit/Templates/frontend.config.template.yaml

@@ -11,9 +11,9 @@ configVersion: 1
 # Just use .ts/.scss extensions in your file paths below - no config needed!
 #
 # CLI Commands:
-#   dotnet frontend dev    - One-time compile of TS/SCSS for development
+#   dotnet frontend dev    - Compile TS/SCSS for development (once)
+#   dotnet frontend watch  - Compile and watch for changes
 #   dotnet frontend build  - Production build with bundling and hashing
-#   dotnet frontend watch  - Watch mode for continuous compilation
 #   dotnet frontend check  - Validate configuration and assets
 # ============================================================================