[GH-ISSUE #1370] TypeError: Cannot read properties of undefined (reading 'ADMIN') #384

Closed
opened 2026-02-26 18:46:47 +03:00 by kerem · 3 comments
Owner

Originally created by @SaurabhGurde on GitHub (Sep 29, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1370

Issue Description

I just cloned the project and first run npm run dx and then npm run dev and suddenly this problem came on my web page. here is screen shot[
Screenshot from 2024-09-29 19-50-38

Steps to Reproduce

No response

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Ubuntu 24

Browser [e.g., Chrome, Firefox]

Google Chrome

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @SaurabhGurde on GitHub (Sep 29, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1370 ### Issue Description I just cloned the project and first run npm run dx and then npm run dev and suddenly this problem came on my web page. here is screen shot[ ![Screenshot from 2024-09-29 19-50-38](https://github.com/user-attachments/assets/b849ccc7-6ae1-4c44-ba1c-beee03971a5e) ### Steps to Reproduce _No response_ ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Ubuntu 24 ### Browser [e.g., Chrome, Firefox] Google Chrome ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [ ] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [X] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved
kerem 2026-02-26 18:46:47 +03:00
Author
Owner

@SaurabhGurde commented on GitHub (Sep 29, 2024):

Issue has been solved but only when i run command "npm run prisma:generate" and then "npm run prisma:migrate-deploy" manually and then restart project again with command "npm run dev"

<!-- gh-comment-id:2381389600 --> @SaurabhGurde commented on GitHub (Sep 29, 2024): Issue has been solved but only when i run command "npm run prisma:generate" and then "npm run prisma:migrate-deploy" manually and then restart project again with command "npm run dev"
Author
Owner

@aditya-chakraborty commented on GitHub (Oct 4, 2024):

Thanks for creating this issue and mentioning the resolution @SaurabhGurde! I also faced the same problem while cloning and running the project locally.

<!-- gh-comment-id:2393429879 --> @aditya-chakraborty commented on GitHub (Oct 4, 2024): Thanks for creating this issue and mentioning the resolution @SaurabhGurde! I also faced the same problem while cloning and running the project locally.
Author
Owner

@ephraimduncan commented on GitHub (Feb 4, 2025):

Closing this as it has been resolved.

<!-- gh-comment-id:2634114431 --> @ephraimduncan commented on GitHub (Feb 4, 2025): Closing this as it has been resolved.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#384
No description provided.