TypeError: cancelable.cancel is not a function
See original GitHub issueDescribe the bug I randomly get this error crashing my application.
To Reproduce
Steps to reproduce the behavior: I don’t know how to reproduce this because it sometimes happens and sometimes does not. It happens immediately when the route in which I load the monaco editor is navigated to.
Expected behavior
I expected it not to crash.
Setting breakpoints to pause on exception does not pause anywhere.
Perhaps by setting break points at all (before monaco loads) I allow it to wait and mount, causing cancellable.cancel
to be a defined function.
Screenshots
Desktop (please complete the following information):
- OS: Both Windows 10 and MacOs 10.15
- Browser: Chrome
- Version: 80
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
angularjs - $cancelRequest is not a function
I'm using angularjs 1.5.8. I get this error when I'm trying to cancel an http request with angular : $cancelRequest is not a...
Read more >Event.cancelable - Web APIs - MDN Web Docs
The cancelable read-only property of the Event interface indicates whether the event can be canceled, and therefore prevented as if the ...
Read more >Cancelling fetch in React and TypeScript | Building SPAs
function assertIsCharacter(data: any): asserts data is Character { if (!("name" in data)) { throw new Error("Not character"); } }.
Read more >Axios Cancel Request
The source.cancel() function takes a single parameter: an optional error message. The error message is just for passing a reason for the ...
Read more >Sortable 'cancel' method raises js error "Uncaught TypeError
The underlying problem is that the cancel method passes a fake event object to _mouseUp... but the fake event is just an object...
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 FreeTop 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
Top GitHub Comments
@suren-atoyan I think the issue still persists in the package due to React 18 strict mode, cause Strict mode simulates mounting and unmounting of components.
Hi @travisdahl. I’ve just published the new version - v3.4.1 🎉 The behavior of that message is fixed. 🙂