Skip to content

Releases: crxjs/chrome-extension-tools

@crxjs/[email protected]

10 Jun 21:23
4541958
Compare
Choose a tag to compare

Patch Changes

  • dc479d1: Fix global constant replacement in background

[email protected]

08 Jun 21:54
234c4d3
Compare
Choose a tag to compare

Patch Changes

@crxjs/[email protected]

08 Jun 21:54
234c4d3
Compare
Choose a tag to compare

Patch Changes

@crxjs/[email protected]

07 Jun 15:59
9bae5d1
Compare
Choose a tag to compare

Patch Changes

  • 8941353: Remove & refactor use of fs-extra

@crxjs/[email protected]

03 Jun 19:31
1beaec6
Compare
Choose a tag to compare

Patch Changes

@crxjs/[email protected]

30 May 22:50
f20bba8
Compare
Choose a tag to compare

Patch Changes

  • e1604d8: Strip paths from content script resource match patterns

@crxjs/[email protected]

26 May 22:04
70e9c02
Compare
Choose a tag to compare

Patch Changes

  • 63d102f: Automatically ignores build.outDir for server HMR, so the file
    writer doesn't trigger a full reload.

    Fixes flaky HMR updates for content scripts; Tailwind should work fine now 🥳

  • a1e2728: Fix isImporter recursion

[email protected]

11 May 17:08
6d0ab24
Compare
Choose a tag to compare

Patch Changes

  • 267c252: chore(rpce) update rollup

@crxjs/[email protected]

09 May 22:22
16cd669
Compare
Choose a tag to compare

Patch Changes

  • 86adbec: Sometimes during development, an extension page may open before the
    service worker has a chance to control fetch. The HTML file will load from the
    file system, but the script tag might load from the dev server. This PR adds a
    precontroller loader plugin to the dev server so that the extension page will
    reload and the fetch handler will get the real HTML file from the server.

@crxjs/[email protected]

09 May 19:55
7ca05d8
Compare
Choose a tag to compare

Patch Changes

  • b83a4bd: Check for manifest assets first in the project root, then check in
    the public dir. Throw an informative error if the file does not exist in
    either dir.