Application Error

I am having an issue with getting my site to be hosted on Vercel. It keeps giving me this application error.

Removing unpermitted intrinsics lockdown-install.js:1:52832
Removing unpermitted intrinsics lockdown-install.js:1:52832
Partitioned cookie or storage access was provided to “https://vercel.live/_next-live/feedback/feedback.html?dpl=dpl_24zR5kCQKF7me5P8ermL8TpGxsyX” because it is loaded in the third-party context and dynamic state partitioning is enabled. contentscript.js:55:11109
TypeError: r is not a function
    NextJS 34
<anonymous code>:1:145535
Removing unpermitted intrinsics lockdown-install.js:1:52832
Partitioned cookie or storage access was provided to “https://vercel.live/_next-live/feedback/feedback.html?dpl=dpl_24zR5kCQKF7me5P8ermL8TpGxsyX” because it is loaded in the third-party context and dynamic state partitioning is enabled. contentscript.js:55:11109
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://charlie-bull-hyga993zn-viktor-khachatryans-projects.vercel.app/<anonymous%20code>
Source Map URL: installHook.js.map

When working on the site locally I do not have any of these errors and the site just works.

This is the github repo:

1 Like

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

I am still getting deployment errors with Vercel. Not sure what is going on. I tried removing the squid router widget entriely, which was the only custom thing I added to the scaffold ETH site. However, it still fails to deploy onto Vercel with build errors most frequent errors.

As an update, I managed to install the widget on vercel via a clean next JS installation. It worked then so I believe it is an issue with scaffold ETH dependencies. If anyone here can shine some light that will be amazing. If not I will be now working on rebuilding the site with a clean Next JS build.

I haven’t seen this particular issue before. Thanks for coming back to share that it worked with a clean Next.js install!