nivo VS DefinitelyTyped

Nivo is a data visualization library built on top of D3.js and React. It offers a range of well-designed, customizable charts with great animations, making it suitable for creating visually impressive data visualizations.

When it comes to charting, Nivo makes you immediately superhero.

Since no one mentioned it, checkout nivo

Today this works thanks to nivo and Cloudinary, but that journey included a lot of trials and testing for the perfect solution.

Nivo is built on D3 and provides a variety of templates for data visualization and presentation. It is one of the few libraries that provide server-side rendering ability and fully declarative charts.

Then, we can think about the implementation. We use Nivo for most data visualizations, but we do have a few that either use straight HTML/CSS, or use D3 directly.

I always use https://nivo.rocks/ you can customize it a ton. Works great.

I use nivo.rocks to visualize the genres and make the list more interactive. Please read my comment on how I implemented it.

CRUD is just one part of the layer. It allows adding/removing/updating data. This is simply a data-foundation for an application.

Of course it feels the same across apps and industries-- it's a concrete slab upon which you build things.

Add layers on top of that, such as:

- Data visualizations. You have data from your CRUD, so do something creative with it. If you're familiar with ReactJS, check out open source, free libraries such as: https://nivo.rocks/ and https://charts.ant.design/

- Data integrations. Depending on the business you're in, experiment with integrating your CRUD app with external data sources via REST API or GraphQL. For example, a CRM like Salesforce or Marketo. Or a REST API in a particular business domain. Or a Google product which a customer might use, such as google drive.

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