@buding0904/vitepad 0.3.0 → 0.3.2

package/README.md

@@ -7,7 +7,7 @@
     <a href="https://www.npmjs.com/package/@buding0904/vitepad"><img src="https://img.shields.io/npm/v/@buding0904/vitepad.svg" alt="npm version" /></a>
     <a href="./LICENSE"><img src="https://img.shields.io/npm/l/@buding0904/vitepad.svg" alt="license" /></a>
     <img src="https://img.shields.io/badge/frameworks-React%20%7C%20Preact%20%7C%20Solid%20%7C%20Vue%20%7C%20Svelte-blue" alt="frameworks" />
-    <img src="https://img.shields.io/badge/Tailwind-v4-38bdf8" alt="Tailwind CSS" />
+    <img src="https://img.shields.io/badge/UnoCSS-enabled-22c55e" alt="UnoCSS" />
   </p>
 </div>
 
@@ -15,7 +15,7 @@
 
 `vitepad` creates a temporary Vite playground for one entry file. Use it to preview a component, test a small main entry, or compare the same file across different framework versions without creating a project or changing the current project's dependencies.
 
-Tailwind CSS is enabled by default. Framework packages are resolved to exact npm versions, downloaded on demand, and cached under `~/.cache/vitepad/frameworks`. No ESLint, Biome, Husky, or formatting pipeline is included.
+UnoCSS is enabled by default. Framework packages are resolved to exact npm versions, downloaded on demand, and cached under `~/.cache/vitepad/frameworks`. No ESLint, Biome, Husky, or formatting pipeline is included.
 
 ## Features
 
@@ -38,11 +38,10 @@ Tailwind CSS is enabled by default. Framework packages are resolved to exact npm
 - Test the same component against different framework versions without touching `package.json`
 - `latest` and semver ranges are resolved to exact versions before caching
 - Cache keys use exact versions, for example `react-19.2.6`
-- `--force-install` recreates the selected framework cache
 
 **Styling and environment**
 
-- Tailwind CSS v4 is available by default through `@tailwindcss/vite`
+- UnoCSS is available by default through `unocss/vite` with `presetUno`
 - Framework dependencies are exposed through the temporary Vite workspace
 - Missing framework packages are linked into local `node_modules` for editor type resolution
 - Existing local packages are left untouched, and `package.json` is not modified
@@ -110,10 +109,9 @@ vitepad <entry> [options]
 |--------|-------------|
 | `<entry>` | Entry file to run |
 | `-f, --framework <name>` | `auto`, `react`, `preact`, `solid`, `vue`, `svelte`, or `vanilla`; version specs are supported, e.g. `react@18` |
-| `--force-install` | Reinstall the selected framework cache |
 | `-p, --port <number>` | Dev server port (default: `8000`) |
+| `--strictPort` | Exit if the configured port is already in use |
 | `--host <host>` | Dev server host (default: `0.0.0.0`) |
-| `--no-open` | Do not open the browser automatically |
 | `-c, --config <file>` | Merge an extra Vite config file |
 | `-h, --help` | Show help |
 
@@ -121,14 +119,14 @@ Examples:
 
 ```bash
 vitepad ./App.tsx --framework react@18 --port 3000
-vitepad ./App.vue --host 127.0.0.1 --no-open
+vitepad ./App.vue --host 127.0.0.1
 vitepad ./App.svelte --config ./vite.extra.js
-vitepad ./App.tsx --framework react@latest --force-install
+vitepad ./App.tsx --framework react@latest
 ```
 
 ## Editor Types
 
-VSCode's TypeScript server resolves imports and JSX types from the opened file's directory tree, not from vitepad's temporary Vite workspace. To keep editor diagnostics aligned with the file you run, vitepad creates lightweight symlinks for missing framework packages inside the entry file directory's `node_modules`.
+VSCode's TypeScript server resolves imports and JSX types from the opened file's directory tree, not from vitepad's temporary Vite workspace. To keep editor diagnostics aligned with the file you run, vitepad looks from the entry file directory up through its parent directories for framework packages before linking anything. If a package cannot be resolved from that directory tree, vitepad creates a lightweight symlink inside the entry file directory's `node_modules`.
 
 For React, vitepad links `react`, `react-dom`, `@types/react`, and `@types/react-dom` when they are missing. Existing packages are left untouched, so a project that already has React installed keeps using its local version for editor types. Runtime dependencies still come from vitepad's cache, and vitepad does not write to `package.json`.