react.dev VS DefinitelyTyped

I mentioned this upthread, but the "official" deprecation notice is this comment from Dan Abramov in a GitHub issue: https://github.com/reactjs/react.dev/pull/5487#issuecomment-...

That has resulted in some interesting github questions before although... it's nothing compared to Java

I found the docs confusing too. Thanks for the quotes; I went ahead and filed an issue here to hopefully get some clarity: https://github.com/reactjs/react.dev/issues/6123

Not a huge thing especially if this is used for learning, but create react app is not the best for starting new react apps. I don't think you need to change anything right now here, but he is some context. If you end up starting a new project, I'd recommend VITE

Also see https://github.com/reactjs/react.dev/issues/3896 and various online articles explaining it.

Then there's this crazy function https://github.com/reactjs/react.dev/issues/3896

Here’s a nice (and quite long) discussion about CRA and Vite, and for those who don’t want to read it all, here’s a comment from Dan Abramov regarding why CRA was created, what is it trying to solve, today’s challenges and its future.

Thank-you for reading, I hope you found this useful! Congratulations to the React team, they have done a great job with the docs. I know they are looking for feedback through their survey and issue tracker, but I’d also love to hear your thoughts on the new docs and let me know what your favourite features are in the comments below 👇

I would advise against using create-react-app in 2023. It still lives in the old docs because those won’t be updated, but the new docs have completely removed the recommendation of create-react-app. New Docs Discussion on downsides

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