Promote CRXJS Vite Plugin from Beta to Latest

[jacksteamdev]

Problem

The @crxjs/vite-plugin is currently at version 2.0.0-beta.32 and needs to be officially released as a stable version. Users are still being instructed to install the beta version in our documentation, and we need to update our release process.

Proposed Solution

We need to complete several tasks to properly promote the beta version to the latest stable release:

• Update documentation references to remove @beta tag

  • Update installation instructions at https://crxjs.dev/vite-plugin/getting-started/react/create-project
  • Update all other framework getting-started pages
  • Update README.md installation examples

• Clean up documentation UI

  • Remove Vite version 2/3 widget from documentation site
  • Ensure compatibility information is clearly stated

• Handle npm release

  • [Take Changesets out of prerelease mode](https://github.com/changesets/changesets/blob/main/docs/prereleases.md)
  • Create a new stable release
  • [Deprecate the last beta version on NPM](https://docs.npmjs.com/cli/v8/commands/npm-deprecate) with a message pointing to the stable version

• Announce the stable release

  • Update GitHub release notes
  • Post announcement in CRXJS Discussion forum

Acceptance Criteria

• Documentation shows stable version in all installation instructions
• NPM package is published with the latest tag
• Previous beta version is properly deprecated with helpful message
• Release is properly announced to users

Alternatives Considered

• Continue using beta versions indefinitely, which would be confusing for users
• Create a major version jump (v3.0.0) instead of finalizing v2.0.0, which isn't necessary since the API is stable

Importance

Medium priority - This is important for user experience but not critical for functionality since the beta version is working well.

[github-actions]

⚠️ Important Notice: CRXJS is seeking new maintainers.

• New issues and PRs may not receive immediate attention
• A new maintenance team must establish itself by March 31, 2025 or this repository will be archived on June 1, 2025
• Learn more about the transition

---

This is an automated message. Please do not reply to this comment.

[AntonOfTheWoods]

Does this mean a new maintenance team has been found?

[Toumash]

@AntonOfTheWoods

Does this mean a new maintenance team has been found?

Updates are here: #974

Timeline

March 31, 2025: Self-organizing maintenance team must be established and working together
March-May 2025: Team demonstrates ability to operate independently
June 1, 2025: If no suitable team is established, repository will be archived

The team is there, now it's about making it work. One more maintainer will be perfect for now

[AntonOfTheWoods]

Ok. I don't see any updates at all on that ticket since Feb 7th, except someone posting a link to a "howto migrate to WXT". I am doing a lot of work on my extension at the moment and now is definitely the time to migrate to another framework for me, if needed. I guess the self-organising team did so on Discord... It would be good to get an update on the ticket you referred to.

[Toumash]

@AntonOfTheWoods
Taking a second look at the issue i see the announcement there #974

I'm happy to announce that @colearendt has joined as the CRXJS Maintenance Team Coordinator! However, we still need additional maintainers to keep the project alive. If CRXJS has been valuable to your work and you'd like to help ensure its future, please DM Cole (colearendt) on Discord to discuss joining the team.

An organizational meeting is coming up, cole will probably post more info soon

[AntonOfTheWoods]

@AntonOfTheWoods Taking a second look at the issue i see the announcement there #974

I'm happy to announce that @colearendt has joined as the CRXJS Maintenance Team Coordinator! However, we still need additional maintainers to keep the project alive. If CRXJS has been valuable to your work and you'd like to help ensure its future, please DM Cole (colearendt) on Discord to discuss joining the team.

An organizational meeting is coming up, cole will probably post more info soon

Hmmm... So we're expected to reread a massive block of text with no specific date attached to the edited portion instead of having a properly dated comment. My bad... I guess? I must be too old for the new communicative styles. Sorry!

[Toumash]

I 100% agree. Added an update there