Scroll breaks on Vercel deployment #17462
Replies: 1 comment
-
Updated packages, issue resolved. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I've got an app landing page in latest Quasar with menu buttons triggering scroll to id, as per the docs.
Code is below. It's a webpack project.
Issue is it works perfectly fine locally with Quasar Dev, but on deployment to Vercel everything else works but the scroll is giving me an error:
vendor.d0888b0b.js:6
TypeError: a is not a function
at v (714.351fbe5f.js:1:2016)
at default.default.default.default.onClick.t..t. (714.351fbe5f.js:1:3428)
at i (vendor.d0888b0b.js:6:11188)
at a (vendor.d0888b0b.js:6:11263)
at Gt (vendor.d0888b0b.js:8:28299)
at k (vendor.d0888b0b.js:69:475263)
at i (vendor.d0888b0b.js:6:11188)
at a (vendor.d0888b0b.js:6:11263)
at HTMLDivElement.r (vendor.d0888b0b.js:14:6970)
I've used this previously and it works on an existing Vercel project, but it's got me stumped why it works locally but is breaking on Vercel build now.
The webpack code looks obfuscated (going by the single character names in the error) but I didn't configure this, which is one thing that seems different and could be the cause of the error.
That's the only difference I can see between local and Vercel deployment.
Has Vercel webpack changed or something in it's default webpack?
Did I miss something else?
I'm following everything here: https://quasar.dev/quasar-utils/scrolling-utils#introduction
Thanks!
Update:
It's very strange it works fine locally, but on deployment to Vercel breaks.
Debugging more it's no longer finding the getScrollTarget(el) function due to something webpack is doing it seems?
Locally it is working fine, and shows the successful debug trace:
Beta Was this translation helpful? Give feedback.
All reactions