Skip to content

Releases: ballercat/jambox

0.4.4 - Static profile dir

14 Nov 15:33
c041ee4
Compare
Choose a tag to compare
  • use a static profile directory

0.4.3

08 Aug 17:30
5eae96f
Compare
Choose a tag to compare
0.4.3

0.4.2

01 Aug 18:30
95e225f
Compare
Choose a tag to compare
  • Housekeeping, upgrade svelte to 4.x

0.4.1

06 May 18:35
a6655cf
Compare
Choose a tag to compare
  • auto change host header when forwarding requests

0.4.0 - Forward config supports arrays

06 May 13:42
fd9d78c
Compare
Choose a tag to compare
  • feat: Users can specify an array for the forward config. This allows mapping different paths of the same domain to different destination origins.

0.3.0

01 May 21:40
bf559a8
Compare
Choose a tag to compare

0.3.0

  • feat: add cors support for forwarded urls

0.2.1

01 May 15:46
aba8ae3
Compare
Choose a tag to compare

Bugfix Release

  • Fix missing Origin headers in Chrome due to --disable-web-security cli flags

0.2.0

08 Mar 15:44
cde31ed
Compare
Choose a tag to compare

Add support for native fetch proxying

This release includes support for proxying (including hitting the cache, stubbing, blocking) requests that use the native fetch within Node.js.

Changes:

  • feat: Support globalThis.fetch proxying, allowing native fetch requests to be cached/stubbed/etc

0.1.3

08 Dec 01:37
Compare
Choose a tag to compare
  • match pathnames with dot('.') literals in them
  • serialize and accept a browser option in config

Turns out that minimatch wont match any string containing a dot(.) character even when given a '**' wildcard blob. That's less than ideal default behavior for path matching in jambox. Also, config wasn't properly serializing the browser value post the refactor update.

0.1.2

20 Nov 20:27
5ab3498
Compare
Choose a tag to compare
  • fix: wait on reset event during config api calls