[GH-ISSUE #1665] Infinite Looping during some commands #473

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

Originally created by @siddnikh on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1665

Issue Description

$ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma
$ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma
$ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma
$ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma
$ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma
$ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma
$ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma
$ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma
$ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma

some commands just go into an infinite loop for some reason. I removed the -w @documenso/prisma to fix that yet it goes there.
Image

It seems like this script in package.json might be causing the issue:

Image

Steps to Reproduce

  1. Clone the repo
  2. run npm run d
  3. get cucked

Expected Behavior

The app should start without falling in an infinite loop and causing js to say you're out of memory.

Current Behavior

falling in an infinite loop and causing js to say you're out of memory.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

MacOS (M1)

Browser [e.g., Chrome, Firefox]

No response

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 @siddnikh on GitHub (Feb 21, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1665 ### Issue Description $ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma $ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma $ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma $ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma $ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma $ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma $ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma $ dotenv -e .env -e .env.local -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma $ bun run with:env -- bun run prisma:migrate-dev -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma -w @documenso/prisma some commands just go into an infinite loop for some reason. I removed the -w @documenso/prisma to fix that yet it goes there. <img width="520" alt="Image" src="https://github.com/user-attachments/assets/a2d9d2f7-999d-4120-ac2d-2a18999c9a79" /> It seems like this script in package.json might be causing the issue: <img width="623" alt="Image" src="https://github.com/user-attachments/assets/a2871630-f013-4c13-816d-4eb8988e1ef8" /> ### Steps to Reproduce 1. Clone the repo 2. run ```npm run d``` 3. get cucked ### Expected Behavior The app should start without falling in an infinite loop and causing js to say you're out of memory. ### Current Behavior falling in an infinite loop and causing js to say you're out of memory. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] MacOS (M1) ### Browser [e.g., Chrome, Firefox] _No response_ ### 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. - [x] I have provided steps to reproduce the issue. - [x] 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
kerem 2026-02-26 18:47:12 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 21, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:2673919674 --> @github-actions[bot] commented on GitHub (Feb 21, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Author
Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

This is issue is probably related to bun. I'm closing this since npm run d works well on the latest version. If you are still facing the same issues, please reopen with a lot more info.

<!-- gh-comment-id:3216276576 --> @ephraimduncan commented on GitHub (Aug 23, 2025): This is issue is probably related to bun. I'm closing this since `npm run d` works well on the latest version. If you are still facing the same issues, please reopen with a lot more info.
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#473
No description provided.