[Bug] TypeError: t.some is not a function
See original GitHub issueWhen adding CodeTool @editorjs/code
, It does cause this bug
I used the example from editorjs.io homepage
Steps to reproduce:
- Go to editorjs.io homepage
- Open the console
- Create a new Code block
- Write something
- You should see the error on the console
Expected behavior: To not throw this error
Screenshots:
Device, Browser, OS: Macbook pro, Chrome, Mac os Big Sur
Editor.js version: “^2.22.2”
Plugins you use with their versions:
"@editorjs/code": "^2.7.0"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:5
Top Results From Across the Web
TypeError: "x" is not a function - JavaScript - MDN Web Docs
The JavaScript exception "is not a function" occurs when there was an attempt to call a value from a function, but the value...
Read more >TypeError: .some Is not A Function React JS Error
The array push operation doesn't return the updated array, Instead, it returns the number of elements in the updated array. This can be...
Read more >Solve - some is not a function in JavaScript - Reactgo
The “some is not a function” error occurs, when we call a some() method on a value which is not array. To fix...
Read more >How to Handle JavaScript Uncaught TypeError: “x” is Not a ...
The Javascript error TypeError: "x" is not a function occurs when there is an attempt to call a function on a value or...
Read more >Custom Field in Editor: Error “TypeError: t.map is not a function”
Hi! All of a sudden I got a problem with Custom Fields. As soon as I try to edit them, this message appears...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same here. Had to rollback to 2.19.3 in a while.
Same Occurs in “The first plugin” example. I think it would occur when plugin has input field, and type-in there.