You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
The text was updated successfully, but these errors were encountered:
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.
Prerelease (v0.X)
app.config.ts
file)webextension-polyfill
by default (#1084)chrome
andbrowser
globals as provided by the browser (#868)Named exports forNot possible, but types are accessible fromchrome
namespace typesbrowser
import (browser.runtime.Sender
) (#932)wxt.config.ts
as ESM #297WXT_
prefix for environment variables (#1076)wxt/storage
into it's own NPM package (#1129)defineRunnerConfig
→defineWebExtConfig
(in prep for creating WXT's own runner, which would usedefineRunnerConfig
andwxt.runner.config.ts
)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!
The text was updated successfully, but these errors were encountered: