@tailwind-merge/vite 0.0.0-dev.50b1d1e9f69ac68604be38dabea94cccdc6b070a

package/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2021 Dany Castillo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,41 @@
+# @tailwind-merge/vite
+
+A [Vite](https://vite.dev) plugin that configures [tailwind-merge](https://github.com/dcastil/tailwind-merge) for your project's own [Tailwind CSS](https://tailwindcss.com) theme — automatically, at build time, with nothing to maintain by hand.
+
+```ts
+// vite.config.ts
+import tailwindcss from '@tailwindcss/vite'
+import tailwindMerge from '@tailwind-merge/vite'
+
+export default {
+    plugins: [tailwindcss(), tailwindMerge()],
+}
+```
+
+```ts
+import { twMerge } from '@tailwind-merge/vite/runtime'
+
+// With `--text-huge: 2.5rem` in your @theme:
+twMerge('text-huge text-sm')
+// → 'text-sm' — plain tailwind-merge would keep both, misreading text-huge as a color
+```
+
+- Zero configuration: your Tailwind CSS entrypoint is auto-detected, the merge config is generated from the theme Tailwind actually resolves
+- One package to add: tailwind-merge is supplied as the plugin's runtime dependency
+- Nothing written to disk: the generated module is served in-memory, so no checked-in artifacts and no TypeScript-server churn
+- Quiet in development: the config regenerates only when your Tailwind configuration changes, and reloads only when the result actually differs
+- Small in production: the config is pruned to the classes found in your sources — the same files Tailwind scans — with substantial savings in the [measured project samples](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/agents/configurator-performance.md)
+- Declares support for Vite 6–8 and the Tailwind CSS v4.3 line; see [coverage limits](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/limitations.md)
+
+> **Status: pre-release, pre-1.0.** There is no stable release yet. Dev builds of every commit on `main` are published to npm under the `dev` tag for evaluation — see [Getting started](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/getting-started.md#availability-and-installation). Treat the plugin as not production-ready until 1.0.0 — see [Versioning](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/versioning.md).
+
+## Get started
+
+- [What is it for](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/what-is-it-for.md)
+- [Getting started](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/getting-started.md)
+- [How it works](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/how-it-works.md)
+- [API reference](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/api-reference.md)
+- [Limitations](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/limitations.md)
+- [Versioning](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/packages/vite/docs/versioning.md)
+
+For work on the plugin itself, read the [Vite development guide](https://github.com/dcastil/tailwind-merge/blob/50b1d1e9f69ac68604be38dabea94cccdc6b070a/agents/vite-plugin.md).

package/dist/index.d.mts

@@ -0,0 +1,58 @@
+import { Plugin } from "vite";
+//#region src/updates.d.ts
+type UpdateTrigger = 'config' | 'sources';
+//#endregion
+//#region src/index.d.ts
+interface TailwindMergeOptions {
+  /** Path to the project's Tailwind CSS entrypoint, relative to the Vite root. When omitted, the entrypoint is auto-detected within the root. Set this to disambiguate themes or select an entrypoint outside the discovery scan. */
+  css?: string;
+  /** LRU cache size of the generated `twMerge`, passed through to the generated config. Defaults to tailwind-merge's default. */
+  cacheSize?: number;
+  /** How theme scales are encoded in the generated config: `'compact'` (default) picks the smallest matcher even when it accepts names beyond the theme, `'exact'` enumerates finite names to avoid that overmatching, at a size cost; arbitrary-value types remain approximate. See the configurator's docs for the tradeoff. */
+  encoding?: 'compact' | 'exact';
+  /**
+   * Prunes the generated config to the classes found in your sources — the same files Tailwind scans, found the same way — so production bundles ship only the class groups and scale values the project uses. Lists composed of scanned candidates merge exactly like with the full generated config; retained validators may also match unscanned names.
+   *
+   * `true` (the default, except in library mode): prune in `vite build`, serve the full config in dev. `false`: never prune — for projects whose class names reach `twMerge` from outside the scanned sources *and* get their styles from somewhere else than this Tailwind build (server-delivered markup, module federation). The object form configures the details.
+   */
+  prune?: boolean | PruneOptions;
+}
+interface PruneOptions {
+  /** Prune production builds. Defaults to `true` — except in library mode (`build.lib`), where the consuming app's classes can't be scanned and the default is `false`. */
+  build?: boolean;
+  /** Also prune in the dev server, for debugging differences between dev and build: every source edit that changes the used classes then regenerates and reloads. Defaults to `false`. */
+  dev?: boolean;
+  /** Log one line per generation saying what pruning did. Defaults to `true`. */
+  log?: boolean;
+}
+/**
+ * What the dev server did in reaction to a file change, reported through `TailwindMergePluginApi.onUpdate` once the plugin has finished processing the change (debounce, regeneration or re-scan, invalidation).
+ */
+interface PluginUpdate {
+  /** Which kind of file changed: one of the CSS graph (`'config'`), or — with `prune.dev` — any other watched file, which may be a source (`'sources'`). */
+  trigger: UpdateTrigger;
+  /** Whether a new module was generated. False when a sources change left the used classes unchanged, and when generation failed and the previous module stays in service. */
+  regenerated: boolean;
+  /** Whether the served module changed and a full reload was sent. False when regeneration produced identical output — the stability gate. */
+  reloaded: boolean;
+}
+/**
+ * The plugin's `api` object (Vite's convention for what a plugin exposes to other plugins and tooling). Lets tooling — and this package's own tests — learn when the dev server has finished reacting to an edit instead of guessing with timeouts.
+ */
+interface TailwindMergePluginApi {
+  /** Subscribes to the dev server's reactions to file changes. Returns the unsubscribe function. */
+  onUpdate(listener: (update: PluginUpdate) => void): () => void;
+}
+/**
+ * Vite plugin that configures tailwind-merge for the project's own Tailwind CSS.
+ *
+ * Add it next to `@tailwindcss/vite` and import from the runtime subpath: `import { twMerge } from '@tailwind-merge/vite/runtime'`. While Vite runs, that import resolves to an in-memory module generated from the project's Tailwind theme by @tailwind-merge/configurator; outside Vite it resolves to the real runtime.ts and serves default tailwind-merge behavior. Repository integration goals and invariants live in agents/vite-plugin.md.
+ *
+ * The dev loop is deliberately quiet: generation reads only the CSS configuration (never which classes the app uses, unless `prune.dev` asks for it), regenerates only when a file of the CSS graph changes, and even then triggers a full reload only when the generated module actually changed — editing utility classes in app.css causes no churn. Production builds additionally prune the config to the classes found in the project's sources (`prune` option).
+ */
+declare function tailwindMerge(options?: TailwindMergeOptions): Plugin & {
+  api: TailwindMergePluginApi;
+};
+//#endregion
+export { PluginUpdate, PruneOptions, TailwindMergeOptions, TailwindMergePluginApi, tailwindMerge as default };
+//# sourceMappingURL=index.d.mts.map

package/dist/index.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.mts","names":[],"sources":["../src/updates.ts","../src/index.ts"],"mappings":";;KAAY;;;UCiBK;;EAEb;;EAEA;;EAEA;;;;;;EAMA,kBAAkB;;UAGL;;EAEb;;EAEA;;EAEA;;;;;UAMa;;EAEb,SAAS;;EAET;;EAEA;;;;;UAMa;;EAEb,SAAS,WAAW,QAAQ;;;;;;;;;iBAUR,cACpB,UAAS,uBACV;EAAW,KAAK"}