Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @lottiefiles/dotlottie-react to ^0.12.0 #832

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@lottiefiles/dotlottie-react (source) ^0.6.5 -> ^0.12.0 age adoption passing confidence

Release Notes

LottieFiles/dotlottie-web (@​lottiefiles/dotlottie-react)

v0.12.3

Compare Source

Patch Changes

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

Patch Changes

v0.12.0

Compare Source

Minor Changes
  • 2c48dbf: refactor: abstract common functionality between DotLottieReact and DotLottieReactWorker to reduce bundle
    size
  • 003e7b1: feat: React v19 upgrade
Patch Changes
  • 2c48dbf: fix: dotLottie instance instantiation and cleanup in React StrictMode for both DotLottieReact and
    DotLottieReactWorker components

v0.11.1

Compare Source

Patch Changes

v0.11.0

Compare Source

Minor Changes
  • fb3ba0f: chore(react): update JSX transform to "react-jsx" and drop React 16 support
Patch Changes

v0.10.1

Compare Source

Patch Changes

v0.10.0

Minor Changes
  • 0d65643: feat: updated dotLottie-rs wasm bindings to v0.1.33 which includes the new v2 dotLottiespecs and theming
    support. feat: Added setSlots methods to DotLottie class to set lottie slots in runtime. feat: Added themeId
    prop to the DotLottie class config to initially load a .lottie with a specific theme. feat: Added resetTheme
    method to the DotLottie class to reset the theme to the default one.

    BREAKING CHANGE:

    • DotLottie's loadTheme method is no longer supported, use setTheme instead.
    • DotLottie's setThemeData method is no longer supported, use setThemeData instead.
Patch Changes

v0.9.3

Patch Changes

v0.9.2

Compare Source

Patch Changes

v0.9.1

Compare Source

Patch Changes

v0.9.0

Compare Source

Minor Changes
  • 40b19ef: chore: update build target from ES2020 to ES2015
Patch Changes

v0.8.12

Compare Source

Patch Changes

v0.8.11

Compare Source

Patch Changes

v0.8.10

Compare Source

Patch Changes

v0.8.9

Compare Source

Patch Changes

v0.8.8

Compare Source

Patch Changes

v0.8.7

Compare Source

Patch Changes
  • 18f8015: fix(react): 🐛 "Worker is not defined" error in Next.js SSR

v0.8.6

Compare Source

Patch Changes

v0.8.5

Compare Source

Patch Changes

v0.8.4

Compare Source

Patch Changes

v0.8.3

Compare Source

Patch Changes
  • b4c4c6b: fix: 🐛 temporarily disable unstable partial canvas rendering optimization in dotLottie-web wrappers

v0.8.2

Compare Source

Patch Changes

v0.8.1

Compare Source

Patch Changes

v0.8.0

Compare Source

Minor Changes
  • eebb307: feat(react): 🎸 add DotLottieWorkerReact component
Patch Changes

v0.7.2

Compare Source

Patch Changes

v0.7.1

Compare Source

Patch Changes

v0.7.0

Compare Source

Minor Changes
  • f0226ec: Feature Update: 🎸 Add optional animationId, themeId, and themeData props to DotLottieReact
    component

    We are excited to introduce new optional props to the DotLottieReact component: animationId, themeId, and
    themeData.

    New Features:

    • animationId: Allows you to specify and render a particular animation from a .lottie file containing multiple
      animations.
    • themeId: Enables the application of a particular theme from the loaded .lottie file to the currently active
      animation.
    • themeData: Allows you to pass custom theme data to the currently active animation.

    Usage Example:

    import { DotLottieReact } from '@​lottiefiles/dotlottie-react';
    import React, { useState, useEffect } from 'react';
    
    const App = () => {
      const [dotLottie, setDotLottie] = useState(null);
      const [animations, setAnimations] = useState([]);
      const [themes, setThemes] = useState([]);
      const [currentThemeId, setCurrentThemeId] = useState('');
      const [currentAnimationId, setCurrentAnimationId] = useState('');
    
      useEffect(() => {
        const onLoad = () => {
          if (dotLottie) {
            setAnimations(dotLottie.manifest.animations || []);
            setThemes(dotLottie.manifest.themes || []);
            setCurrentAnimationId(dotLottie.activeAnimationId);
            setCurrentThemeId(dotLottie.activeThemeId);
          }
        };
    
        dotLottie?.addEventListener('load', onLoad);
    
        return () => {
          dotLottie?.removeEventListener('load', onLoad);
        };
      }, [dotLottie]);
    
      return (
        <div>
          <DotLottieReact dotLottieRefCallback={setDotLottie} animationId={currentAnimationId} />
          <label>Theme:</label>
          {currentThemeId && (
            <select value={currentThemeId} onChange={(e) => setCurrentThemeId(e.target.value)}>
              {themes.map((theme) => (
                <option key={theme.id} value={theme.id}>
                  {theme.id}
                </option>
              ))}
            </select>
          )}
          <label>Animation:</label>
          {currentAnimationId && (
            <select value={currentAnimationId} onChange={(e) => setCurrentAnimationId(e.target.value)}>
              {animations.map((animation) => (
                <option key={animation.id} value={animation.id}>
                  {animation.id}
                </option>
              ))}
            </select>
          )}
        </div>
      );
    };
  • a564ff0: perf(react): ⚡️ render only visible canvas area

    This update optimizes the rendering performance by ensuring that only the visible portion of the canvas is rendered,
    utilizing the dotlottie-web setViewport API.

    Note: No changes are required for existing usage. The optimization is applied internally within the DotLottieReact
    component.

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge January 30, 2025 07:08
Copy link
Contributor Author

renovate bot commented Jan 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
➤ YN0000: · Yarn 4.6.0
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @lottiefiles/dotlottie-react@npm:0.12.3, @lottiefiles/dotlottie-web@npm:0.40.1
➤ YN0085: │ - @lottiefiles/dotlottie-react@npm:0.6.5, @lottiefiles/dotlottie-web@npm:0.25.0, debounce@npm:2.2.0
➤ YN0000: └ Completed in 1s 521ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ @lottiefiles/dotlottie-react is listed by your project with version 0.12.3 (pf2a39), which doesn't satisfy what lottie-react-native requests (~0.6.5).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 2 packages were added to the project (+ 5.01 MiB).
➤ YN0000: └ Completed in 0s 251ms
➤ YN0000: ┌ Link step
➤ YN0073: │ Skipped due to mode=update-lockfile
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 2s 24ms

@renovate renovate bot force-pushed the renovate/lottiefiles-dotlottie-react-0.x branch 19 times, most recently from 135d5e3 to cfe03ff Compare February 6, 2025 07:03
@renovate renovate bot force-pushed the renovate/lottiefiles-dotlottie-react-0.x branch 5 times, most recently from 0f976fc to 92ec8da Compare February 10, 2025 23:32
@renovate renovate bot force-pushed the renovate/lottiefiles-dotlottie-react-0.x branch from 92ec8da to 6388861 Compare February 11, 2025 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants