Skip to content

v0.18.0

Compare
Choose a tag to compare
@github-actions github-actions released this 04 May 15:51
· 41 commits to main since this release

compare changes

πŸš€ Enhancements

  • Add zip compression settings (#605)
  • Support returning values from scripts executed with the scripting API (#624)
  • experimental: Load entrypoint options with Vite Runtime API (#648)

🩹 Fixes

  • ⚠️ Automatically move host_permissions to permissions for MV2 (#626)
  • dep: Upgrade @webext-core/isolated-element to v1.1.2 (#625)

πŸ“– Documentation

  • Add Fluent Read to homepage (#600)
  • Fix typo on example for wxt.config.ts. (#609)
  • Tix typo in entrypoints.md (#614)
  • Add Facebook Video Controls to homepage (#615)
  • Fix typo in assets page (a94d673)
  • Add ElemSnap to homepage (#621)
  • Update content script registration JSDoc (e47519f)
  • Add docs about handling updates (acb7554)
  • Add MS Edge TTS to homepage (#647)
  • Document required permission for storage API (#632)

🏑 Chore

  • Update vue template config (#607)
  • deps-dev: Bump lint-staged from 15.2.1 to 15.2.2 (#637)
  • deps-dev: Bump publint from 0.2.6 to 0.2.7 (#639)
  • deps-dev: Bump simple-git-hooks from 2.9.0 to 2.11.1 (#640)
  • Refactor repo to a standard monorepo (#646)
  • Fix formatting after monorepo refactor (6ca3767)

⚠️ Breaking Changes

  • ⚠️ Automatically move host_permissions to permissions for MV2 (#626)

    Out of an abundance of caution, I've marked this as a breaking change because permission generation has changed. If you list host_permissions in your wxt.config.ts's manifest and have released your extension, double check that your permissions and host_permissions have not changed for all browsers you target in your .output/*/manifest.json files. Permission changes can cause the extension to be disabled on update, and can cause a drop in users, so be sure to double check for differences compared to the previous manifest version.

❀️ Contributors