Skip to content

Uncaught TypeError: Cannot read properties of undefined (reading 'lazyPreloaderClass') #7935

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

Open
6 tasks done
BerkeAras opened this issue Mar 28, 2025 · 2 comments · May be fixed by #7936
Open
6 tasks done

Uncaught TypeError: Cannot read properties of undefined (reading 'lazyPreloaderClass') #7935

BerkeAras opened this issue Mar 28, 2025 · 2 comments · May be fixed by #7936

Comments

@BerkeAras
Copy link

Check that this is really a bug

  • I confirm

Reproduction link

https://codesandbox.io/p/devbox/swiper-default-forked-6c96g3?workspaceId=ws_NcfeSzfz6N96RJW7VKTnaL

Bug description

We are getting an error Uncaught TypeError: Cannot read properties of undefined (reading 'lazyPreloaderClass').

Due to our complex case (combining VueJS with other technologies) we cannot reproduce the issue.

Expected Behavior

No response

Actual Behavior

No response

Swiper version

11.2.6

Platform/Target and Browser Versions

macOS Arc Browser, same issue on Windows/Linux/iOS/Android and on other browsers too.

Validations

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR
@Scribilicious
Copy link

Yes, it’s a rare issue. I stumbled upon it as well. Hopefully, they accept your pull request or find another way to fix this issue, since it’s spamming my error log.

@BerkeAras
Copy link
Author

BerkeAras commented Mar 28, 2025

Yes, it’s a rare issue. I stumbled upon it as well. Hopefully, they accept your pull request or find another way to fix this issue, since it’s spamming my error log.

Could you find any fix until the PR is merged & released? @Scribilicious

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 a pull request may close this issue.

2 participants