Vite 4 support about unplugin-swc HOT 4 CLOSED

Hrm, I see.

unplugin-swc does have a dependency on unplugin.

{
  "dependencies": {
    "unplugin": "^0.6.0"
  },
}

Which resolves to version 0.6.3 as that's the latest 0.6.x release. And that specific version has a peer dependency on vite.

{
  "peerDependencies": {
    ...
    " vite": "^2.3.0"
  }
}

Which indeed resolves to 2.9.16. Using yarn 1.22.19, which did not warn me about the missing peer deps, since vite is marked as an optional peer dependency in unplugin.

https://github.com/unjs/unplugin/blob/29fe515d424101970e14c3296eb99a2d553055f7/package.json#L76

You should be able to remove that particular vite version from your package-lock.json / yarn.lock and make sure version 4.x.x is used instead.

from unplugin-swc.

What issue are you experiencing with Vite 4?

I described how to use Vitest + this plugin for a NestJS app here:

https://github.com/geersch/nestjs-getting-started/blob/main/docs/12-vitest.md

Bumped into a few issues (see caveats / known issues), but nothing related to Vite 4.

from unplugin-swc.

@geersch

For me, unplugin-swc is using [email protected]

from unplugin-swc.

This should fixed in v1.4.0, give it a try!

from unplugin-swc.