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

Hi folks this is React Oxide. It's a minimal code editor that runs in a browser. MIT licensed, code at: https://github.com/bootrino/reactoxide I wrote React Oxide because I needed a simple code editor but couldn't find something that included editor, tabs, a file tree and file management. You can see a YouTube demo at https://youtu.be/OmxKAWeN38I You can see a live demo at https://www.reactoxide.com It use the Microsoft Monaco editor https://microsoft.github.io/monaco-editor/ It's written in TypeScript. The React code is written in a style I call "Event driven React", which means inter component communication is done via event emitters rather than using global or lifted state. So state is almost entirely managed at a component level. I did this because I find state to make React applications complex and hard to debug, whereas this event