Skip to content

Releases: markwylde/workerbox

v6.4.3

01 Feb 11:03
5dfcb8d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.4.2...v6.4.3

v6.4.2

04 Jan 21:21
2a0f327
Compare
Choose a tag to compare
  • Upgrade dependencies

v6.4.1

30 Dec 10:03
cadb15c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.4.0...v6.4.1

v6.4.0

16 Nov 07:51
c727c4a
Compare
Choose a tag to compare

What's Changed

  • feat: improve types and use SuperJSON for serialization and deserialization by @TomerAberbach in #35

New Contributors

Full Changelog: v6.3.2...v6.4.0

v6.3.2

07 Nov 07:58
40a01f3
Compare
Choose a tag to compare
  • upgrade debounce

v6.3.1

01 Oct 21:35
0f0485e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.3.0...v6.3.1

v6.3.0

02 Aug 19:27
02b8f75
Compare
Choose a tag to compare

What's Changed

Full Changelog: v6.2.0...v6.3.0

v6.2.0

29 Jun 13:39
000961a
Compare
Choose a tag to compare
  • Upgrades dependencies
  • Downgrades minify temporarily as it's breaking functionality

Full Changelog: v6.1.1...v6.2.0

v6.1.1

30 Jun 20:58
17e6901
Compare
Choose a tag to compare

A project using esbuild with code splitting wasn't working correctly, as the format had to change to esm, meaning the export default wasn't getting transpiled.

Anyway, I've broke out the export for the build in workerbox "server", which should now bundle correctly.

v6.0.0

04 Apr 20:44
052b010
Compare
Choose a tag to compare
  • Embed a sandbox worker

We no longer need to add a serverUrl to run the script on a separate domain thanks to the sandbox attribute on the iframe.

Previously we had to do this:

const { run } = await createWorkerBox('https://sandbox.workerbox.net');

Whereas now we can do:

const { run } = await createWorkerBox();

If you still want to run the sandbox from the workerbox.net domain, you can update your code to:

const { run } = await createWorkerBox({
  serverUrl: 'https://sandbox.workerbox.net',
  appendVersion: true
});