Please note that this repository contains no source code for the code editor, it only contains the scripts to package everything together and ship the
monaco-editor npm module.
Try it out
Try the editor out on our website.
$ npm install monaco-editor
You will get:
esm: ESM version of the editor (compatible with e.g. webpack)
dev: AMD bundled, not minified
min: AMD bundled, and minified
min-maps: source maps for
monaco.d.ts: this specifies the API of the editor (this is what is actually versioned, everything else is considered private and might break with any release).
It is recommended to develop against the
dev version, and in production to use the
- Learn how to integrate the editor with these complete samples.
- Learn how to use the editor API and try out your own customizations in the playground.
- Explore the API docs or read them straight from
- Read this guide to ensure the editor is accessible to all your users!
- Create a Monarch tokenizer for a new programming language in the Monarch playground.
- Ask questions on StackOverflow! Search open and closed issues, there are a lot of tips in there!
Create issues in this repository for anything related to the Monaco Editor. Always mention the version of the editor when creating issues and the browser you’re having trouble in. Please search for existing issues to avoid duplicates.
In IE 11, the editor must be surrounded in the body element, otherwise the hit testing performed for mouse operations does not work. You can inspect this using F12 and click on the body element and confirm that visually it surrounds the editor.
❓ What is the relationship between VS Code and the Monaco Editor?
The Monaco Editor is generated straight from VS Code’s sources with some shims around services the code needs to make it run in a web browser outside of its home.
❓ What is the relationship between VS Code’s version and the Monaco Editor’s version?
None. The Monaco Editor is a library and it reflects directly the source code.
❓ I’ve written an extension for VS Code, will it work on the Monaco Editor in a browser?
❓ Why all these web workers and why should I care?
Language services create web workers to compute heavy stuff outside of the UI thread. They cost hardly anything in terms of resource overhead and you shouldn’t worry too much about them, as long as you get them to work (see above the cross-domain case).
❓ What is this
loader.js? Can I use
It is an AMD loader that we use in VS Code. Yes.
❓ I see the warning “Could not create web worker”. What should I do?
HTML5 does not allow pages loaded on
file:// to create web workers. Please load the editor with a web server on
https:// schemes. Please also see the cross-domain case above.
❓ Is the editor supported in mobile browsers or mobile web app frameworks?
❓ Why doesn’t the editor support TextMate grammars?
- All the regular expressions in TM grammars are based on oniguruma, a regular expression library written in C.
- The only way to interpret the grammars and get anywhere near original fidelity is to use the exact same regular expression library (with its custom syntax constructs).
- In Monaco, we are constrained to a browser environment where we cannot do anything similar.
- We have experimented with Emscripten to compile the C library to asm.js, but performance was very poor even in Firefox (10x slower) and extremely poor in Chrome (100x slower).
- We can revisit this once WebAssembly gets traction in the major browsers, but we will still need to consider the browser matrix we support, i.e. if we support IE11 and only Edge will add WebAssembly support, what will the experience be in IE11, etc.
Please see CONTRIBUTING
Code of Conduct
Licensed under the MIT License.