starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

bcrypt_lib.node' #157

New issue

Closed

opened 2026-02-26 18:45:38 +03:00 by kerem · 9 comments

kerem commented

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

Owner

Originally created by @TameemAsim on GitHub (Oct 23, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/592

Getting following error:
Error: Cannot find module '/workspace/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node'

Issue Description

On sending request to api, Getting following error:
Error: Cannot find module '/home/tameem/Desktop/18feb06/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node'

Steps to Reproduce

start server
send request to api

Expected Behavior

Should work normally.

Current Behavior

Giving following error:
Cannot find module '/workspace/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node'

Environment

OS: ubuntu 22.04
Browser: Chrome

Checklist

[ 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 understand that this is a voluntary contribution and that there is no guarantee of resolution.

Originally created by @TameemAsim on GitHub (Oct 23, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/592 Getting following error: Error: Cannot find module '/workspace/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node' ## Issue Description On sending request to api, Getting following error: Error: Cannot find module '/home/tameem/Desktop/18feb06/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node' ## Steps to Reproduce 1. start server 2. send request to api ## Expected Behavior Should work normally. ## Current Behavior Giving following error: Cannot find module '/workspace/documenso/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node' ## Environment - OS: ubuntu 22.04 - Browser: Chrome ## Checklist - [ 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 understand that this is a voluntary contribution and that there is no guarantee of resolution.

kerem closed this issue

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

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 23, 2023):

I would love to solve this.

@TameemAsim commented on GitHub (Oct 23, 2023): I would love to solve this.

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Oct 24, 2023):

Can you run this and try again?

npm run reset:hard

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

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 24, 2023):

@dephraiim I have tried this but it is not working.
I know its due to bcrypt version "^5.1.1".
If we remove bcrypt from package.json as it was before. It will work normally. I removed bcrypt from package.json and then installed all packages. Then it started working normally.

@TameemAsim commented on GitHub (Oct 24, 2023): @dephraiim I have tried this but it is not working. I know its due to bcrypt version "^5.1.1". If we remove bcrypt from package.json as it was before. It will work normally. I removed bcrypt from package.json and then installed all packages. Then it started working normally.

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 24, 2023):

Kindly allow me to solve this

@TameemAsim commented on GitHub (Oct 24, 2023): Kindly allow me to solve this

kerem commented

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

Author

Owner

@Mythie commented on GitHub (Oct 24, 2023):

That won't be the issue though sorry. Could you confirm the Node.js version you're using right now?

bcrypt has been a dep for some time and no recent changes should have broken that, looking at the package-lock.json I can see that there's nothing that could be causing a realm error or similar.

@Mythie commented on GitHub (Oct 24, 2023): That won't be the issue though sorry. Could you confirm the Node.js version you're using right now? `bcrypt` has been a dep for some time and no recent changes should have broken that, looking at the `package-lock.json` I can see that there's nothing that could be causing a realm error or similar.

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 24, 2023):

node version: 18.17.1

@TameemAsim commented on GitHub (Oct 24, 2023): node version: 18.17.1

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 25, 2023):

Closed this issue because it is solved

@TameemAsim commented on GitHub (Oct 25, 2023): Closed this issue because it is solved

kerem commented

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

Author

Owner

@Mythie commented on GitHub (Oct 25, 2023):

Apologies, what was the fix on your end?

@Mythie commented on GitHub (Oct 25, 2023): Apologies, what was the fix on your end?

kerem commented

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

Author

Owner

@TameemAsim commented on GitHub (Oct 25, 2023):

To remove "bcrypt": "^5.1.1" from main package.json file, which is already done

@TameemAsim commented on GitHub (Oct 25, 2023): To remove "bcrypt": "^5.1.1" from main package.json file, which is already done

kerem referenced this issue

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

[PR #157] [CLOSED] feat: introduce Input component #763

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

No description provided.

Rows
Columns