starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 22:05:59 +03:00

[GH-ISSUE #687] Failed when run `npm run dx` with NodeJS 18.18.0 and NPM 8.19.2 #196

New issue

Closed

opened 2026-02-26 18:45:50 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 18:45:50 +03:00

Owner

Originally created by @ducle-infotrack on GitHub (Nov 26, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/687

Issue Description

Hi mates, I got this issue when try to install documenso. Can you guys give it a try?

OS: Window 10
Node: 18.18.2
NPM: 8.19.2

 npm run dx

> dx
> npm i && npm run dx:up && npm run prisma:migrate-dev

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @documenso/marketing@0.1.0
npm ERR! Found: next@14.0.0
npm ERR! node_modules/next
npm ERR!   next@"14.0.0" from @documenso/marketing@0.1.0
npm ERR!   apps/marketing
npm ERR!     @documenso/marketing@0.1.0
npm ERR!     node_modules/@documenso/marketing
npm ERR!       workspace apps\marketing from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^12.2.5 || ^13" from next-auth@4.24.3
npm ERR! node_modules/next-auth
npm ERR!   next-auth@"4.24.3" from @documenso/marketing@0.1.0
npm ERR!   apps/marketing
npm ERR!     @documenso/marketing@0.1.0
npm ERR!     node_modules/@documenso/marketing
npm ERR!       workspace apps\marketing from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\infotrack.vn\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\infotrack.vn\AppData\Local\npm-cache\_logs\2023-11-26T16_44_34_522Z-debug-0.log

Steps to Reproduce

run npm run dx

Expected Behavior

To be end up successfully

Current Behavior

To be end up in below error

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Windows 10

Browser [e.g., Chrome, Firefox]

Bash

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 @ducle-infotrack on GitHub (Nov 26, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/687 ### Issue Description Hi mates, I got this issue when try to install documenso. Can you guys give it a try? - OS: Window 10 - Node: 18.18.2 - NPM: 8.19.2 ```bash npm run dx > dx > npm i && npm run dx:up && npm run prisma:migrate-dev npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: @documenso/marketing@0.1.0 npm ERR! Found: next@14.0.0 npm ERR! node_modules/next npm ERR! next@"14.0.0" from @documenso/marketing@0.1.0 npm ERR! apps/marketing npm ERR! @documenso/marketing@0.1.0 npm ERR! node_modules/@documenso/marketing npm ERR! workspace apps\marketing from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer next@"^12.2.5 || ^13" from next-auth@4.24.3 npm ERR! node_modules/next-auth npm ERR! next-auth@"4.24.3" from @documenso/marketing@0.1.0 npm ERR! apps/marketing npm ERR! @documenso/marketing@0.1.0 npm ERR! node_modules/@documenso/marketing npm ERR! workspace apps\marketing from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See C:\Users\infotrack.vn\AppData\Local\npm-cache\eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\infotrack.vn\AppData\Local\npm-cache\_logs\2023-11-26T16_44_34_522Z-debug-0.log ``` ### Steps to Reproduce run `npm run dx` ### Expected Behavior To be end up successfully ### Current Behavior To be end up in below error ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Windows 10 ### Browser [e.g., Chrome, Firefox] Bash ### 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. - [X] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [X] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:45:50 +03:00

closed this issue
added the
type: bug

Stale
labels

kerem commented

2026-02-26 18:45:50 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Nov 26, 2023):

Can you run this and try again?

npm run reset:hard

@ephraimduncan commented on GitHub (Nov 26, 2023): Can you run this and try again? ``` npm run reset:hard ```

kerem commented

2026-02-26 18:45:50 +03:00

Author

Owner

@Mythie commented on GitHub (Nov 26, 2023):

Gday, this is due to our next 14 upgrade. I’ll get it sorted this morning! 🙌🏻

@Mythie commented on GitHub (Nov 26, 2023): Gday, this is due to our next 14 upgrade. I’ll get it sorted this morning! 🙌🏻

kerem commented

2026-02-26 18:45:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 27, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

@github-actions[bot] commented on GitHub (Dec 27, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

kerem commented

2026-02-26 18:45:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 3, 2024):

This issue has been closed because of inactivity.

@github-actions[bot] commented on GitHub (Jan 3, 2024): This issue has been closed because of inactivity.

kerem referenced this issue

2026-02-26 18:48:55 +03:00

[PR #196] [MERGED] feat: reset password #787

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#196

No description provided.

Rows
Columns

[GH-ISSUE #687] Failed when run npm run dx with NodeJS 18.18.0 and NPM 8.19.2 #196

Issue Description

Steps to Reproduce

Expected Behavior

Current Behavior

Screenshots (optional)

Operating System [e.g., Windows 10]

Browser [e.g., Chrome, Firefox]

Version [e.g., 2.0.1]

Please check the boxes that apply to this issue report.

[GH-ISSUE #687] Failed when run `npm run dx` with NodeJS 18.18.0 and NPM 8.19.2 #196