Unmaintained?

[Malix-off]

Hello folks, is this project still maintained?

The docs tells that

CRXJS support for Vite 3 is in beta

https://crxjs.dev/vite-plugin/getting-started/vanilla-js/create-project#create-a-project

Altough vite 3 released July 23, 2022, and now it is at v5.1.4

Also, CRXJS latest release is Aug 11, 2022 and vite-plugin v2 is in beta since a year and a half

[Toumash]

Yes it is - the beta version works really well for me with vite 3, 4 and 5.
The question i have currently is - when are we going to be out of beta?

For HMR: im not sure if there are issues with vite 4 but for me it didnt work because of multiple exports - its like that by design. To prevent it use eslint rule https://github.com/ArnaudBarre/eslint-plugin-react-refresh and it should work flawlessy

[Unit2795]

Works for me just fine with Vite 5, React, and Typescript. Though I am getting a warning when I manage my dependencies. I am using PNPM 9.1.0. Interested to see if this library gets any updates. If anyone ends up finding a newer alternative, keep us all posted. Thank you!

 WARN  Issues with peer dependencies found
.
└─┬ @crxjs/vite-plugin 1.0.14
  └── ✕ unmet peer vite@^2.9.0: found 5.2.12

[Malix-off]

If anyone ends up finding a newer alternative, keep us all posted

The two main alternatives are WXT and Plasmo
I did go with WXT personally

[Unit2795]

If anyone ends up finding a newer alternative, keep us all posted

The two main alternatives are WXT and Plasmo I did go with WXT

Wow, these are fantastic. Thanks a million for sharing! 👍

[Toumash]

WXT does NOT support HMR as is does not have a major version yet. Its a big no-no for me.
Plasmo has a strange implicit way of defining entrypoints but from the github issues it looks like it works (havent tried it yet)
@Unit2795 you have outdated @crxjs/vite-plugin - install the beta release (i dont consider it a beta - i have it for a year on my production) npm i -D @crxjs/vite-plugin@beta

[Malix-off]

WXT does NOT support HMR as is does not have a major version yet. Its a big no-no for me.

https://wxt.dev/guide/development.html#:~:text=separately%20when%20possible.-,HMR,-Reloaded%20individually

A big no for me is no release in 2y ngl

[cpakken]

I wonder how @jacksteamdev is doing? He really made a very useful vite plugin and I think it's still the best way to build chrome extensions to this day even though it's currently unmaintained. I haven't had any major issues with the beta versions. Getting HMR working even with injected content scripts works well. Service workers, content scripts refreshes correctly on save, vite builds bundles assets nicely. What more can you ask for?

Though I wish for some sort of status update from @jacksteamdev on the future of this plugin.