Roadmap to v1.0

[!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
  • #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
  • #1627
  • #1629
  • https://github.com/wxt-dev/wxt/pull/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)
• 🚧 #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)
• https://github.com/wxt-dev/wxt/issues/1195
• 🚧 https://github.com/wxt-dev/wxt/issues/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!

Start with the linked v1.0 milestone and its unresolved issues; this issue is a high-level checklist rather than an implementation entry point. Review the remaining runtime-configuration item for app.config.ts environment-variable integration and the listed open issues. Done means the applicable milestone work is resolved and the roadmap is updated.