[Bug]: useEmblaCarousel initializes Embla with stale options in certain cases

[lesha1201]

Which variants of Embla Carousel are you using?

• embla-carousel (Core)
• embla-carousel-react
• embla-carousel-vue
• embla-carousel-svelte
• embla-carousel-autoplay
• embla-carousel-auto-scroll
• embla-carousel-solid
• embla-carousel-auto-height
• embla-carousel-class-names
• embla-carousel-fade
• embla-carousel-docs (Documentation)
• embla-carousel-docs (Generator)

Steps to reproduce

The issues happens when useEmblaCarousel creates EmblaCarousel (emblaApi) at the same time when options have changed. It happens because of useEffect order

Here is an example: https://codesandbox.io/p/devbox/embla-carousel-stale-options-dw88yj

If you open the example on small viewport (less than 1024px in width) then the issue appears and Embla Carousel wrongly initialized with watchDrag: false instead of watchDrag: true.

Desktop.2024.08.21.-.17.57.47.01.mp4

Expected Behavior

Embla Carousel should be initialized with the latest options.

Additional Context

I have also tried...

What browsers are you seeing the problem on?

All browsers

Version

v8.2.0

CodeSandbox

https://codesandbox.io/p/devbox/embla-carousel-stale-options-dw88yj

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues
• I agree to follow this project's Contributing Guidelines for bug reports

[lesha1201]

I will open PR shortly.

[davidjerleke]

@lesha1201 why aren’t you using the breakpoints option?

[lesha1201]

@davidjerleke Didn't know about breakpoints options. Thanks for pointing it out.

However, the issue can happen in other cases where useEmblaCarousel starts initializing EmblaCarousel and at the same time the options have been changed. In this case, it will initialize it with the previous options.

• I opened PR [Bug]: useEmblaCarousel initializes Embla with stale options in certain cases #981 that just changes the order of useEffects.

[davidjerleke]

@lesha1201 thanks. I will look into this when possible.

[davidjerleke]

@lesha1201 thanks. Your PR solves the problem.

[davidjerleke]

@lesha1201 this bug fix was released in v8.2.1.