Building a better online editor for TypeScript • Hacker News Board

Re: Building a better online editor for TypeScript

#11

Post by whazor » Thu, Sep 25, 2025, 11:57 AM UTC

d357r0y3r wrote: post #7

rafram wrote: post #2

Why not Monaco? It works great. https://github.com/microsoft/monaco-editor

I've built significant applications using Monaco, including things that tie into custom LSPs. They really just should have used Monaco. This will be a burden to maintain and won't be a core differentiator.

Codemirror nowadays has first-party LSP support: https://github.com/codemirror/lsp-client

Re: Building a better online editor for TypeScript

#12

Post by rafram » Fri, Sep 26, 2025, 2:31 AM UTC

whazor wrote: post #10

rafram wrote: post #2

Why not Monaco? It works great. https://github.com/microsoft/monaco-editor

CodeMirror 6 is more modern with better accessibility and variable width fonts.

CodeMirror 6 is more modern than the editor that powers VS Code?

Re: Building a better online editor for TypeScript

#13

Post by gvkhna » Fri, Sep 26, 2025, 8:01 PM UTC

WorldMaker wrote: post #9

gvkhna wrote: post #8

Earlier quoted context omitted.

yet They could have also contributed to the effort. You can also add types to monaco typescript. I don’t see a need for a Deno specific LSP, am I missing something?

The biggest deal difference between the Deno LSP and Typescript sort-of-LSP in my experience is around the import model. Typescript has a bunch of "module resolution" modes based on various combinations of browser, bundler, and/or Node. For various reasons the Deno LSP is the only encoding of the Deno "module resolution' and upstream Typescript doesn't have a "denoX" set of "module resolution" options. The second big…

Ah interesting, Yes i see what you’re saying regarding eslint and didn’t consider that. I’m a big of newer linters with better perf but none match the depth currently with eslint. Will keep an eye out on deno lsp!