You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is the right place for this but also I haven't found any other written evidence of what we experienced yesterday so I thought I'd put it here in case anyone comes across it in the future.
We have an internal project based off Laravel, Vite, Inertia, and Vue and its been going really well.
Yesterday we found that it just straight up stopped working but only on the recently released Chrome 129. It worked in Chrome 128 on our colleagues computers who hadn't updated and it worked for me in Chrome 130 (installing the unstable version). No other browser seemed affected.
It worked in development mode (vite) but not when built for production (vite build). A few console logs proved that the setup function given to createIntertiaApp was not running.
The only thing which seemed to work was using a const to store the return of createInertiaApp and then making sure it wasn't shaken away during the build.
It looks like there were some important security fixes in Chrome 129 so perhaps our code fell into a very specific niche gap but then that gap was closed for the now-upcoming next version.
Hope this is useful for someone else out there (or there is a more obvious fix which is slightly less chaotic).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't know if this is the right place for this but also I haven't found any other written evidence of what we experienced yesterday so I thought I'd put it here in case anyone comes across it in the future.
We have an internal project based off Laravel, Vite, Inertia, and Vue and its been going really well.
Yesterday we found that it just straight up stopped working but only on the recently released Chrome 129. It worked in Chrome 128 on our colleagues computers who hadn't updated and it worked for me in Chrome 130 (installing the unstable version). No other browser seemed affected.
It worked in development mode (
vite
) but not when built for production (vite build
). A few console logs proved that thesetup
function given tocreateIntertiaApp
was not running.The only thing which seemed to work was using a
const
to store the return ofcreateInertiaApp
and then making sure it wasn't shaken away during the build.It looks like there were some important security fixes in Chrome 129 so perhaps our code fell into a very specific niche gap but then that gap was closed for the now-upcoming next version.
Hope this is useful for someone else out there (or there is a more obvious fix which is slightly less chaotic).
Beta Was this translation helpful? Give feedback.
All reactions