|
1 | 1 | # @vanilla-extract/vite-plugin
|
2 | 2 |
|
| 3 | +## 5.0.0 |
| 4 | + |
| 5 | +### Major Changes |
| 6 | + |
| 7 | +- [#1537](https://github.com/vanilla-extract-css/vanilla-extract/pull/1537) [`7810b7c`](https://github.com/vanilla-extract-css/vanilla-extract/commit/7810b7c8b8344dc2b5618b25d2945ecc3d81b469) Thanks [@askoufis](https://github.com/askoufis)! - Change the plugin name from `"vanilla-extract"` to the more [conventional][plugin conventions] `"vite-plugin-vanilla-extract"` |
| 8 | + |
| 9 | + [plugin conventions]: https://vite.dev/guide/api-plugin.html#conventions |
| 10 | + |
| 11 | +- [#1529](https://github.com/vanilla-extract-css/vanilla-extract/pull/1529) [`d5b6e70`](https://github.com/vanilla-extract-css/vanilla-extract/commit/d5b6e70f44a3d4f03e113fe78e0605b358e9c0d7) Thanks [@askoufis](https://github.com/askoufis)! - Update `vite` peer dependency range to `^5.0.0 || ^6.0.0` |
| 12 | + |
| 13 | + BREAKING CHANGE: Vite 4 is no longer supported. Please upgrade to at least Vite 5. |
| 14 | + |
| 15 | +- [#1537](https://github.com/vanilla-extract-css/vanilla-extract/pull/1537) [`7810b7c`](https://github.com/vanilla-extract-css/vanilla-extract/commit/7810b7c8b8344dc2b5618b25d2945ecc3d81b469) Thanks [@askoufis](https://github.com/askoufis)! - BREAKING CHANGE: User-configured vite plugins are no longer forwarded through to the Vanilla Extract compiler by default. This should not affect most consumers. |
| 16 | + |
| 17 | + Previously, all vite plugins except for a select few incompatible plugins were forwarded through. This resulted in a constant game of whack-a-mole as new plugins were added to the list of incompatible plugins as issues were discovered. |
| 18 | + |
| 19 | + Framework-specific plugins, as well as plugins that handle assets and build output, tend not to be relevant to Vanilla Extract code, and in some cases cause more harm than good. |
| 20 | + |
| 21 | + For that reason, in this release only the `vite-tsconfig-paths` plugin is fowarded through by default. This is a relatively common plugin that is know to be compatible with the Vanilla Extract compiler. |
| 22 | + |
| 23 | + In most cases users should not need to forward any additional plugins through to the Vanilla Extract compiler. However, if such a case arises, a plugin filter function can be provided via the `unstable_pluginFilter` option: |
| 24 | + |
| 25 | + ```ts |
| 26 | + // vite.config.ts |
| 27 | + |
| 28 | + import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin'; |
| 29 | + import { vitePluginFoo } from 'vite-plugin-foo'; |
| 30 | + |
| 31 | + export default defineConfig({ |
| 32 | + plugins: [ |
| 33 | + vitePluginFoo(), |
| 34 | + vanillaExtractPlugin({ |
| 35 | + // Only forward the `vite-plugin-foo` plugin through to the Vanilla Extract compiler |
| 36 | + unstable_pluginFilter: ({ name, mode }) => |
| 37 | + plugin.name === 'vite-plugin-foo' |
| 38 | + }) |
| 39 | + ] |
| 40 | + }); |
| 41 | + ``` |
| 42 | + |
| 43 | + When providing a plugin filter function, the `vite-tsconfig-paths` plugin will no longer be forwarded through by default. If you wish to forward this plugin, you must include it in your filter function. |
| 44 | + |
| 45 | + **NOTE**: The `unstable_pluginFilter` API is considered unstable and may be changed or removed without notice in a future non-major version. |
| 46 | + |
| 47 | +### Patch Changes |
| 48 | + |
| 49 | +- Updated dependencies [[`d5b6e70`](https://github.com/vanilla-extract-css/vanilla-extract/commit/d5b6e70f44a3d4f03e113fe78e0605b358e9c0d7), [`d5b6e70`](https://github.com/vanilla-extract-css/vanilla-extract/commit/d5b6e70f44a3d4f03e113fe78e0605b358e9c0d7)]: |
| 50 | + - @vanilla-extract/compiler@0.1.1 |
| 51 | + |
3 | 52 | ## 4.0.20
|
4 | 53 |
|
5 | 54 | ### Patch Changes
|
|
0 commit comments