build(deps): bump @lottiefiles/dotlottie-web from 0.18.0 to 0.28.0

[dependabot]

Bumps @lottiefiles/dotlottie-web from 0.18.0 to 0.28.0.

Release notes

Sourced from @​lottiefiles/dotlottie-web's releases.

@​lottiefiles/dotlottie-web@​0.28.0

Minor Changes

• 1d26a93: feat(web): 🎸 DotLottieWorker

  Introducing DotLottieWorker, a new class for offloading animation rendering to a Web Worker, enhancing application performance by freeing the main thread from expensive animations rendering. The API remains similar to DotLottie, with most methods being asynchronous.

  Basic Usage

  import { DotLottieWorker } from '@lottiefiles/dotlottie-web';
  new DotLottieWorker({
  canvas: document.getElementById('canvas'),
  src: 'url/to/animation.json',
  autoplay: true,
  loop: true,
  });

  Worker Grouping

  By default, all animations using DotLottieWorker are rendered in the same worker. To group animations into different workers, use the workerId property in the configuration object, as shown below:

  new DotLottieWorker({
    canvas: document.getElementById('canvas'),
    src: 'url/to/animation.json',
    autoplay: true,
    loop: true,
    workerId: 'worker-1',
  });
  new DotLottieWorker({
  canvas: document.getElementById('canvas-2'),
  src: 'url/to/animation2.json',
  autoplay: true,
  loop: true,
  workerId: 'worker-2',
  });

  This feature is particularly useful when rendering a large number of animations simultaneously, as it allows you to distribute the rendering animations workload across multiple workers, improving performance.

@​lottiefiles/dotlottie-web@​0.27.0

Minor Changes

... (truncated)

Changelog

Sourced from @​lottiefiles/dotlottie-web's changelog.

0.28.0

Minor Changes

• 1d26a93: feat(web): 🎸 DotLottieWorker

  Introducing DotLottieWorker, a new class for offloading animation rendering to a Web Worker, enhancing application performance by freeing the main thread from expensive animations rendering. The API remains similar to DotLottie, with most methods being asynchronous.

  Basic Usage

  import { DotLottieWorker } from '@lottiefiles/dotlottie-web';
  new DotLottieWorker({
  canvas: document.getElementById('canvas'),
  src: 'url/to/animation.json',
  autoplay: true,
  loop: true,
  });

  Worker Grouping

  By default, all animations using DotLottieWorker are rendered in the same worker. To group animations into different workers, use the workerId property in the configuration object, as shown below:

  new DotLottieWorker({
    canvas: document.getElementById('canvas'),
    src: 'url/to/animation.json',
    autoplay: true,
    loop: true,
    workerId: 'worker-1',
  });
  new DotLottieWorker({
  canvas: document.getElementById('canvas-2'),
  src: 'url/to/animation2.json',
  autoplay: true,
  loop: true,
  workerId: 'worker-2',
  });

  This feature is particularly useful when rendering a large number of animations simultaneously, as it allows you to distribute the rendering animations workload across multiple workers, improving performance.

0.27.0

... (truncated)

Commits

• d155322 chore(web): 🤖 fix flaky DotLottieWorker tests (#281)
• 8ca8fd9 chore(web): 🤖 fix DotLottieWorker failing tests (#280)
• e61d099 chore: 🤖 update versions (#279)
• 1d26a93 feat(web): 🎸 DotLottieWorker (#242)
• 7b8f3e5 chore: 🤖 update versions (#270)
• 4c0bcd6 feat(web): 🎸 added DotLottie ready event (#267)
• d6354a9 chore: update versions (#263)
• ba46fd1 feat(web): 🎸 added loadStateMachineData & animationSize & state machine conte...
• d7c2c20 fix(web): 🐛 skip triggering LoadEvent for already loaded animations (#256)
• 24d4528 chore: 🤖 update versions (#255)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #97.