Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Adding Extra lib execution to fast for key naming convention
See original GitHub issuemonaco-editor version: 0.9.0 Browser: Google Chrome Version 61.0.3154.0 (Official Build) canary (64-bit) OS: Windows 10 Enterprise Steps assume monaco editor is already installed and createEditor has already been called. Steps or JS usage snippet reproducing the issue:
Load libraries statically:
// this._typescriptExtraLibs is used to dispose later
this._typescriptExtraLibs = monaco.languages.typescript.typescriptDefaults.addExtraLib(person.toString());
this._typescriptExtraLibs = monaco.languages.typescript.typescriptDefaults.addExtraLib(animal.toString());
this._typescriptExtraLibs = monaco.languages.typescript.typescriptDefaults.addExtraLib(flee.toString());
this._typescriptExtraLibs = monaco.languages.typescript.typescriptDefaults.addExtraLib(color.toString());
Receive error at: line 39, column 1220 (minified script) Error: Uncaught Error: ts:extralib-1499848020086 already a extra lib My conclusion: I stepped through the code and notice that due to the way that the keys in the this._extraLibs are generated using the date it has conflicts due to “too fast” processing.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@JohannWNel That indeed solved it. Thanks a lot!
Closing as this will not be fixed.