[GH-ISSUE #220] Module not found: Can't resolve 'yjs' #87

Open
opened 2026-03-01 14:39:58 +03:00 by kerem · 6 comments
Owner

Originally created by @batrdn on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/arikchakma/maily.to/issues/220

Am I the only one having this issue? I've just installed maily-to/core and getting this error, which seems to be coming from y-prosemirror library

Originally created by @batrdn on GitHub (Sep 16, 2025). Original GitHub issue: https://github.com/arikchakma/maily.to/issues/220 Am I the only one having this issue? I've just installed `maily-to/core` and getting this error, which seems to be coming from `y-prosemirror` library
Author
Owner

@arikchakma commented on GitHub (Sep 16, 2025):

How come, I am using this in production.

Can you show me the whole error? Maybe clean the node_modules and install again.

<!-- gh-comment-id:3299157956 --> @arikchakma commented on GitHub (Sep 16, 2025): How come, I am using this in production. Can you show me the whole error? Maybe clean the node_modules and install again.
Author
Owner

@batrdn commented on GitHub (Sep 16, 2025):

I'm using next@13.5.9, node v22 with yarn@1.22

../../node_modules/y-prosemirror/src/lib.js:3:0
Module not found: Can't resolve 'yjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
../../node_modules/y-prosemirror/src/y-prosemirror.js
../../node_modules/@maily-to/core/dist/index.mjs
<!-- gh-comment-id:3299232839 --> @batrdn commented on GitHub (Sep 16, 2025): I'm using next@13.5.9, node v22 with yarn@1.22 ``` ../../node_modules/y-prosemirror/src/lib.js:3:0 Module not found: Can't resolve 'yjs' https://nextjs.org/docs/messages/module-not-found Import trace for requested module: ../../node_modules/y-prosemirror/src/y-prosemirror.js ../../node_modules/@maily-to/core/dist/index.mjs ```
Author
Owner

@arikchakma commented on GitHub (Sep 16, 2025):

It would be really helpful if you would provide a minimal reproduction.

<!-- gh-comment-id:3299246602 --> @arikchakma commented on GitHub (Sep 16, 2025): It would be really helpful if you would provide a minimal reproduction.
Author
Owner

@batrdn commented on GitHub (Sep 16, 2025):

I'm just importing import {Editor} from "@maily-to/core", and using the editor without any props.

import {Editor} from "@maily-to/core"

function Page() {
     return <Editor />
}
<!-- gh-comment-id:3299276808 --> @batrdn commented on GitHub (Sep 16, 2025): I'm just importing `import {Editor} from "@maily-to/core"`, and using the editor without any props. ```tsx import {Editor} from "@maily-to/core" function Page() { return <Editor /> } ```
Author
Owner

@arikchakma commented on GitHub (Sep 16, 2025):

I haven’t been able to reproduce the issue myself, and we’re also running it in production without seeing the problem. If you could prepare a minimal reproduction, I’d be happy to debug it further.

<!-- gh-comment-id:3299298327 --> @arikchakma commented on GitHub (Sep 16, 2025): I haven’t been able to reproduce the issue myself, and we’re also running it in production without seeing the problem. If you could prepare a minimal reproduction, I’d be happy to debug it further.
Author
Owner

@ennioVisco commented on GitHub (Jan 8, 2026):

@batrdn you are using a version of Yarn that was released 6 years ago (latest maintenance patch 2 years ago).
I'd recommend switching to a newer package manager and see if that solves the problem

<!-- gh-comment-id:3724477375 --> @ennioVisco commented on GitHub (Jan 8, 2026): @batrdn you are using a version of Yarn that was released 6 years ago (latest maintenance patch 2 years ago). I'd recommend switching to a newer package manager and see if that solves the problem
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/maily.to#87
No description provided.