Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: On press enter raise an error #579

Open
ahmedabdelhafez opened this issue Sep 22, 2024 · 4 comments
Open

[Bug]: On press enter raise an error #579

ahmedabdelhafez opened this issue Sep 22, 2024 · 4 comments

Comments

@ahmedabdelhafez
Copy link

What happened?

Hello,
when i press enter to go to next line the edtor raie this error in the console
image

Version

15.3.0

Angular Version

15.2.5

What browsers are you seeing the problem on?

Firefox, Chrome

Link to reproduce

No response

Relevant log output

No response

Willing to submit a PR?

None

@sibiraj-s
Copy link
Owner

Can you try deleting your node_modules and reinstalling the package. what package manager are you using, if manual dedupe is supported, you can try running that once?

@df-nextre
Copy link

I have the same problem when clicking any botton not just "enter", I've already tried deleting and reinstalling the node_modules but it didn't work
immagine

@kgbpixelque
Copy link

Enter Key Behavior in ngx-editor Results in Unexpected Errors
Description:

When using the ngx-editor, pressing the Enter key after entering a single character or number causes an unexpected error. The editor requires two presses of the Enter key to insert a line break, which disrupts the user experience.

Steps to Reproduce:

Open the ngx-editor.
Press the Enter key.

Screenshot from 2024-10-22 12-54-34

@pawelpiotrowski
Copy link

pawelpiotrowski commented Oct 23, 2024

Same issue for me with 15.3.0 and angular 16. Looks like this occurs only in app when packages or text-editor were recently installed (using same version) with npm.
In ex.

  • app X with dependencies installed ~1 year ago works fine
  • app Y with dependencies installed few days ago works throws mentioned error

Changes between those apps can be seen in package-lock.json updated after installation. Looks like multiple versions are result of prosemirror-transform, see:

OLD INSTALL

"node_modules/prosemirror-transform": {
  "version": "1.8.0",
  "resolved": "...",
  "integrity": "...",
  "license": "MIT",
  "dependencies": {
    "prosemirror-model": "^1.0.0"
  }
},

=======================
LATEST INSTALL

"node_modules/prosemirror-transform": {
  "version": "1.9.0",
  "resolved": "...",
  "integrity": "...",
  "license": "MIT",
  "dependencies": {
    "prosemirror-model": "^1.21.0"
  }
},
"node_modules/prosemirror-transform/node_modules/prosemirror-model": {
  "version": "1.21.3",
  "resolved": "...",
  "integrity": "...",
  "license": "MIT",
  "dependencies": {
    "orderedmap": "^2.0.0"
  }
},

In both cases prosemirror-model are declared as 1.19.0

"node_modules/prosemirror-model": {
  "version": "1.19.0",
  "resolved": "...",
  "integrity": "...",
  "license": "MIT",
  "dependencies": {
    "orderedmap": "^2.0.0"
  }
},

I hope it helps @sibiraj-s any update on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants