-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[Bug] Error since v1.45.0 #5352
Comments
๐ @bentwnghk Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
The error message "ReferenceError: Cannot access 'm' before initialization" typically indicates that a variable is being used before it has been properly initialized. This can occur due to issues in the code where the variable is referenced before its declaration or assignment. To address this issue, you can try the following steps:
If the issue persists, you may need to look into the specific logic or functions involved in the affected code sections to ensure proper initialization order. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
๐ฆ Environment
Docker
๐ Version
v1.45.0
๐ป Operating System
Ubuntu
๐ Browser
Chrome
๐ Bug Description
Docker log:
`๐ DNS Server: [ '127.0.0.11' ]
[Database] Start to migration...
โ database migration pass.
โฒ Next.js 15.1.4
Local: http://localhost:3210
Network: http://0.0.0.0:3210
โ Starting...
โ Ready in 45ms
{
allowDangerousEmailAccountLinking: true,
clientId: undefined,
clientSecret: undefined,
platformType: 'WebsiteApp',
profile: [Function: profile]
}
(node:28) [DEP0040] DeprecationWarning: The
punycode
module is deprecated. Please use a userland alternative instead.(Use
node --trace-deprecation ...
to show where the warning was created)ReferenceError: Cannot access 'm' before initialization
โจฏ unhandledRejection: ReferenceError: Cannot access 'm' before initialization
๐ท Recurrence Steps
No response
๐ฆ Expected Behavior
No response
๐ Additional Information
No response
The text was updated successfully, but these errors were encountered: