modern-editor VS DefinitelyTyped

> "building a text-annotation based app"

I'm going to assume that you are talking about a desktop-based webapp that is also responsive, and not a native app. I also believe you when you say that you do not know where you are getting into.

I have 10+ years of experience doing front-end, with probably over a dozen React packages self-published in npm, and also tried making a rich text editor ~6 years back[1]. I actually recommend starting with no framework at all (please read on).

Creating a rich text editor might be the hardest thing you can do in "normal" front-end (excluding some more advanced "frontend" fields like 3D or games). You can either manipulate raw cursors, which will be very tricky because I'm not even sure you have access to all the right APIs (specially on mobile), or you can attempt to use Contenteditable, which is a hell of its own[2].

"All problems start with caret placing and multi browser support" [3]

That said, I believe 90% of the complexity of your app will be here, around the actual interaction with the or <div contenteditable> that you will be using. For that, no framework will really help you, at all. So my recommendation is to first get that working, which will take weeks/months and hundreds or thousands of lines of code, and then worry about placing the little hovering boxes in their place (the "UI"), which is like 10 lines of JS/CSS[4].<p>[1] <a href="https://github.com/franciscop/modern-editor" rel="nofollow">https://github.com/franciscop/modern-editor</a><p>[2] <a href="https://answerly.io/blog/my-pain-developing-a-wysiwyg-editor-with-contenteditable/" rel="nofollow">https://answerly.io/blog/my-pain-developing-a-wysiwyg-editor...</a><p>[3] <a href="https://news.ycombinator.com/item?id=27938702" rel="nofollow">https://news.ycombinator.com/item?id=27938702</a><p>[4] <a href="https://stackoverflow.com/q/4495626/938236" rel="nofollow">https://stackoverflow.com/q/4495626/938236</a>

Prior to React 18, it used to include an implicit children prop, making it suitable for components expected to have children. For a long time, though, the implicit children prop type has been removed according to React 18's type changes.

Additionally, because TypeScript has a well established and widely used install-base, there are already many different definition files in the wild for supporting non-TypeScript supporting projects. One of the more extensive collections of these typings lives at the DefinitelyTyped repository, which publishes the package's community typings under the package names @types/your-package-name (where your-package-name is the name of the project you're looking for typings of) that you can look for on your package manager.

View on GitHub

Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill

Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

type NumberOrString = number | string; type Status = "idle" | "loading" | "success" | "failure" // React useState, can receive a value or a function as parameter to serve as initial value. // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a03856975a17eba524739676affbf70ac4078176/types/react/v17/index.d.ts#L920 function useState(initialState: S | (() => S)): [S, Dispatch>];

The TypeScript pull request was merged, so Sebastian (who helps maintain the React type definitions) exercised new powers in this pull request to the DefinitelyTyped repository for the React type definitions. At the time of writing, this pull request is still open, but once merged and shipped the React community we will feel its benefits.

there is an open issue: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/61616

Relatively infrequently. Normally, if an npm package is popular and doesn’t have its own types, there will be a community provided types declaration file available from https://github.com/DefinitelyTyped/DefinitelyTyped