Roadmap to v1.0

[aklinker1]

Important

Please refer to the v1.0 milestone for the official list of issues that have been created and that need resolved. This milestone includes bugs and small improvements not listed below.

Hello everyone, we're getting super close to WXT v1.0 and I want to share a public roadmap for how we'll get there. Below are the high-level features I want to implement before v1.0 is released.

🚧 indicates a potentially breaking change

Prerelease (v0.X)

• File system based manifest generation
• Frontend Framework support
• Module System
  • Initial implementation (#672)
  • Runtime Configuration (app.config.ts file)
    • Basic implementation (#792)
    • Env var integration
  • Cleanup and document module execution order #1070
  • In-depth examples
    • Vue (#716)
    • Svelte (#726)
    • React (#729)
    • Solid (#730)
    • Auto-icons (#851)
    • I18n (#758)
    • Analytics (#790)
  • Recipes for common patterns (#933)
  • Double check the template repo is ready to go: https://github.com/wxt-dev/module-template
  • [Module API] Filter which entrypoints plugins run in #1627
  • [WXT Modules] Automatically add build and runtime options without manual module augmentation #1629
  • fix: Re-initialize WXT modules correctly during development #1176
• 🚧 Don't use webextension-polyfill by default (#1084)
  • Experimental setting to use chrome and browser globals as provided by the browser (#868)
  • Update manifest config typing (#521)
  • Named exports for chrome namespace types Not possible, but types are accessible from browser import (browser.runtime.Sender) (#932)
• 🚧 Load wxt.config.ts as ESM #297
• Use WXT_ prefix for environment variables (#1076)
• Extract wxt/storage into it's own NPM package (#1129)
• Finish documenting all the incomplete pages (#933)
• 🚧 API Renaming
  • defineRunnerConfig → defineWebExtConfig (in prep for creating WXT's own runner, which would use defineRunnerConfig and wxt.runner.config.ts)
• Apply CSS reset inside shadow roots #1195
• 🚧 Make Vite a Peer Dependency  #1631

Release Candidate (v1.0.0-rcX)

No alpha/beta, we're going straight into release candidates. Here, we're focusing on bugs and performance. At this point, there will be no more breaking changes and there might only be small features added.

There will probably be 1 month's worth of release candidates, and as long as everything is looking stable, I'll release v1.0!

[mrshappy0]

@aklinker1 After spending a day attempting to get the @wxt-dev/analytics to work with either umami or GA4, I'm wondering if this feature is still in-progress. By the way, great work on this push to v1.0. Loving the progress so far.

[aklinker1]

@aklinker1 After spending a day attempting to get the @wxt-dev/analytics to work with either umami or GA4, I'm wondering if this feature is still in-progress. By the way, great work on this push to v1.0. Loving the progress so far.

Yes, the analytics package is in prerelease as well because I expect the public API to change as people try it out.

However, I use GA4 in production and it works great, but it's in a closed source work project, so I can't share the exact code. that said, the code is exactly what the docs say to use... So not sure what's going on in your case.

However, for the purpose of WXT 1.0, the analytics WXT module is good to go (ignoring the runtime code) and serves as a good example of how to do things.

[juliomuhlbauer]

Why not wxt becomes a Vite Plugin?
#1894

[Arktomson]

Is it still being iterated and updated?

[aklinker1]

Is it still being iterated and updated?

@Arktomson Yes. WXT has gotten so popular that my time is mostly spent answering people's questions and fixing bugs, not adding new features. Plus I have less time to work on it due to my real job changing. So things have slowed down, and I'm stuck at the 90% complete mark lol

Refer to the milestone for a list of all issues that need to be completed.

[Arktomson]

Is it still being iterated and updated?

@Arktomson Yes. WXT has gotten so popular that my time is mostly spent answering people's questions and fixing bugs, not adding new features. Plus I have less time to work on it due to my real job changing. So things have slowed down, and I'm stuck at the 90% complete mark lol

Refer to the milestone for a list of all issues that need to be completed.

It's really great that maintenance is still continuing, and I hope I can participate in the maintenance and development of new features in the future.

[aklinker1]

If you're interested in becoming a maintainer and helping out, send me an email! I am very happy to add new maintainers to the project to help out.

https://github.com/wxt-dev/wxt/blob/main/CONTRIBUTING.md#become-a-maintainer

[Arktomson]

If you're interested in becoming a maintainer and helping out, send me an email! I am very happy to add new maintainers to the project to help out.

https://github.com/wxt-dev/wxt/blob/main/CONTRIBUTING.md#become-a-maintainer

Okay, I need to first familiarize myself with the entire repository, then try to resolve some issues, and afterward submit a maintainer application to you.

[aklinker1]

Checkout the "Contribution welcome" issues! Would love for anyone to pick any of them up.

https://github.com/wxt-dev/wxt/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22contribution%20welcome%22

Some already have PRs... Reviewing them would help me out a ton as well.