AwaitRenderStatus is not defined in production with nextjs

[jiayuxiaochaoren]

AwaitRenderStatus is not defined in production with nextjs

[beinoriusju]

I've had the exact same issue with AwaitRenderStatus error that started occurring just last week. My intuition says that some lib in the chain of dependencies of Nextjs dependencies got updated and this caused a memory leak inside app.

My plan was to load ReactAdmin component dynamically (just like you load lifi/widget). While in development it worked it became unusually slow (to a degree tests started failing). But when build for production it stopped working all-together giving AwaitRenderStatus error.

Unfortunately I was not able to resolve it neither with [email protected] nor [email protected], but upgrading to 13.5.2 solved this problem.

[chybisov]

@jiayuxiaochaoren Hey, thanks for reporting the issue. Could you please provide a reproducible example? AwaitRenderStatus is not something we have in our code, and maybe this comes from one of the dependencies.

[jiayuxiaochaoren]

Thank you for your reply.
This is my package.json:
{
"version": "0.0.1",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint --fix"
},
"dependencies": {
"@aws-sdk/client-s3": "^3.319.0",
"@aws-sdk/lib-storage": "^3.319.0",
"@chakra-ui/icons": "^2.0.19",
"@chakra-ui/react": "^2.5.5",
"@chakra-ui/styled-system": "^2.6.1",
"@chakra-ui/theme": "^2.2.4",
"@emotion/react": "^11.10.6",
"@emotion/styled": "^11.10.6",
"@infura/sdk": "^2.4.3",
"@lifi/widget": "^2.4.4",
"@socket.tech/plugin": "^1.3.0",
"@supabase/supabase-js": "^2.12.1",
"@tabler/icons": "^1.86.0",
"@types/js-cookie": "^3.0.3",
"@vercel/analytics": "^1.0.1",
"@vercel/kv": "^0.2.2",
"arraybuffer-to-buffer": "^0.0.7",
"cross-fetch": "^3.1.5",
"dayjs": "^1.11.7",
"ethereum-blockies-base64": "^1.0.2",
"ethers": "^5.7.2",
"framer-motion": "^10.3.1",
"fs": "0.0.1-security",
"ipfs-http-client": "^60.0.1",
"js-cookie": "^3.0.1",
"next": "^13.1.6",
"next-auth": "^4.19.2",
"next-transpile-modules": "^10.0.1",
"omit-deep": "^0.3.0",
"prettier": "^2.8.8",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-helmet": "^6.1.0",
"react-icons": "^4.8.0",
"siwe": "^2.1.4",
"swr": "^2.2.0",
"url-loader": "^4.1.1",
"uuid": "^9.0.0",
"viem": "^1.3.1",
"wagmi": "^1.3.9"
},
"devDependencies": {
"@babel/core": "^7.18.13",
"@types/node": "^18.7.11",
"@types/react": "^18.0.28",
"dotenv": "^16.0.1",
"eslint": "^8.22.0",
"eslint-config-next": "^13.1.6",
"eslint-config-prettier": "^8.8.0",
"tsx": "^3.8.2",
"typescript": "5.1.6"
},
"peerDependencies": {
"@babel/core": "^7.18.13"
}
}
and code:
import { LiFiWidget } from '@lifi/widget'
import dynamic from 'next/dynamic'
// import { WidgetEvents } from './WidgetEvents'
const LiFiWidgetDynamic = dynamic(
() => import('@lifi/widget').then((module) => module.LiFiWidget) as any,
{
ssr: false
},
) as typeof LiFiWidget
export const Widget = () => {
return (
<>
{/* */}
<LiFiWidgetDynamic
config={{
fromChain: 324,
variant: 'default',
subvariant: 'split',
appearance: 'light',
languages: { default: 'en' },
containerStyle: {
width: '100%',
border: '1px solid rgb(234, 234, 234)',
borderRadius: '16px',
// margin: '0px 16px',
minWidth: '360px'
}
}}
integrator="zkproject"
/>
</>
)
}
by the way my project use Vercel to deploy.

@jiayuxiaochaoren Hey, thanks for reporting the issue. Could you please provide a reproducible example? AwaitRenderStatus is not something we have in our code, and maybe this comes from one of the dependencies.

[chybisov]

@beinoriusju thank you for providing such a detailed insight! 🙏 @jiayuxiaochaoren I hope that helps 🙂