reactoxide VS Monaco Editor

It's a minimal code editor that runs in a browser. MIT licensed, code at: https://github.com/bootrino/reactoxide

The EventEmitter pattern seems interesting! I can't say I've wrapped my head around it enough to weigh the benefits and drawbacks. I would point out a few things after a quick look:

* It looks like you're creating an emitter wrapper around an EventEmitter instance, freezing it, then exporting the instance rather than the frozen wrapper[0]. I see .on() and .off() are wrapped here, while the project appears to use .addListener() and .removeListener() instead.

* As a typescript project, I would recommend using typed-emitter[1]. Not only does it ensure you're only emitting recognized events, it ensures that the type of the payload is correct for the corresponding event. Currently, your typed handlers are coercing from `any` as far as your IDE is concerned, rendering it unable to help prevent you from mistakes.

* Instead of plumbing an emitter prop everywhere, even through components that don't interact with it directly, this looks like a better fit for the Context pattern to create the global emitter instance in a top-level context provider, then getting a reference to the emitter via useContext[2].

[0] https://github.com/bootrino/reactoxide/blob/master/reactoxid...

[1] https://www.npmjs.com/package/typed-emitter

[2] https://reactjs.org/docs/context.html

Fyi, if you are ever looking for a fun project you might be able to implement this. The vscode editor source is available as a library https://microsoft.github.io/monaco-editor/

VScode uses the monaco-editor to display all editor screens in vscode including the markdown editor. A simple solution is to use the in built markdown file editor and call it a day.

visual studio is open source: https://github.com/microsoft/vscode

i remember using their monaco editor as well (https://github.com/microsoft/monaco-editor), a really powerful editor & the very same used by VS Code (i think you can even get at the AST for TypeScript, for example, in the browser if you poke around deep enough)

crazy cool stuff, and most definitely OSS!!!

So lets say the project consists of two packages Lib and App in which Lib is a library and App is the frontend app which depends on Lib. Now I want to display a monaco powered code editor in App which has has access to all types of Lib. This means that I have to somehow read the *.d.ts file of Lib as a string to set it as "extra lib" for monaco.

WebView webView = new WebView(); webView.getEngine().load("https://microsoft.github.io/monaco-editor/");

You’ll see a Monaco Editor-powered change editor. The content incoming from the Git repo is on the left, while the current content in Vrite is on the right. You can make changes in the editor on the right - this will ultimately become the result content. Once you’re done, click Resolve. If there are no other conflicts, you should now be able to pull the latest changes.

From googling about it seems that Azure uses monaco editor to make code in repos be colourised and what not. this appears to be the editor library for vscode, so that makes sense.

By referencing the ProseMirror docs, forwarding the editor state back and forth, and adjusting the layout, I managed to integrate Monaco Editor — the web editor extracted from VS Code — together with Prettier (for code formatting) right into the Vrite Editor (I know, that’s a lot of editors in one place 😅).

mozes koristiti gotovi code editor library, https://codemirror.net/ https://microsoft.github.io/monaco-editor/