The Monaco Editor is the code editor that powers VS Code, a good page describing the code editor’s features is here.
Try it out
See the editor in action here.
Learn how to extend the editor and try out your own customizations in the playground.
Browse the latest editor API at
Please mention the version of the editor when creating issues and the browser you’re having trouble in. Create issues in this repository.
In IE, the editor must be completely surrounded in the body element, otherwise the hit testing we do for mouse operations does not work. You can inspect this using F12 and clicking on the body element and confirm that visually it surrounds the editor.
npm install monaco-editor
You will get:
dev: bundled, not minified
min: 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
Here is the most basic HTML page that embeds the editor. More samples are available at monaco-editor-samples.
Integrate cross domain
If you are hosting your
.js on a different domain (e.g. on a CDN) than the HTML, you should know that the Monaco Editor creates web workers for smart language features. Cross-domain web workers are not allowed, but here is how you can proxy their loading and get them to work:
Read this guide to ensure the editor is accessible to all your users!
Find full HTML samples here.
Create a Monarch tokenizer here.
❓ 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 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
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact email@example.com with any additional questions or comments.