Skip to content

Releases: preactjs/preset-vite

2.1.7

28 Dec 11:09
Compare
Choose a tag to compare

Create safer ending check by not excluding git substring #38 thanks @JoviDeCroock

2.1.6

23 Dec 09:14
Compare
Choose a tag to compare

2.1.5

18 Oct 20:39
Compare
Choose a tag to compare

Bug Fixes

  • Fix import specifiers with query parameters not being processed correctly. This avoids processing virtual modules in Vue single-file components (thanks @ElMassimo, #26)

2.1.4

13 Oct 16:55
Compare
Choose a tag to compare

Bug Fixes

  • Switch from jsxInject to automatic jsx-runtime transform (thanks @JoviDeCroock, #25)

Full Changelog: v2.1.3...v2.1.4

2.1.3

04 Oct 21:48
Compare
Choose a tag to compare
  • Fix ES-Module entry point using wrong extension in import source #23

2.1.2

27 Sep 18:01
Compare
Choose a tag to compare
  • Add both CommonJS and ES Module entry points to support all environments.

2.1.1

27 Sep 09:48
Compare
Choose a tag to compare
  • Fix compatibility with vite >=2.5

2.1.0

18 Apr 14:17
Compare
Choose a tag to compare

Features

screenshot-after

Bug Fixes

2.0.1

24 Mar 09:44
Compare
Choose a tag to compare

Bug Fixes

2.0.0

15 Mar 19:19
Compare
Choose a tag to compare

Releasing this preset to the public sparked a discussion on how presets should be done in vite in general. It turns out that plugins can be an array of plugins and that this is the intended approach moving forward. Since this project is very new it was deemed better to do this breaking change now, rather than later when the userbase will be significantly larger.

To update change your vite configuration from wrapping your config:

import withPreact from "@preact/preset-vite";

export default withPreact({
  // Your vite config
});

..to moving it to the plugin array:

import { defineConfig } from "vite";
import preact from "@preact/preset-vite";

export default defineConfig({
  plugins: [preact()]
});

Breaking

Bug Fixes