wmr VS nivo

wmr for near-instant builds & native TS support

Preferred tech stack is always something I choose for the job at hand. That might just be a few rollup plugins + a tool like WMR or Vite, but it can be also be quite complex and custom build system too. It depends.

While the development process is evolving for developers, there’s a need by many developers to have an all-in-one development tool that will make web application development faster and easier. WMR gives developers the added feature and advantage of building web applications based on the all-in-one development tool.

wmr does not have error overlay / SVGR support

It did not take a lot of time to choose the tool. Currently, there are 3 major bundlers powered by ESM - vite, snowpack, and wmr. From the first glance - all of them look promising and I did not care about their internals as long as I don't need to touch them.

WMR could be another option if you haven’t already seen it.

wmr is an all-in-one development tool for modern web apps. Since it leverages ESM modules, it only requires an HTML files with

Thanks! I'll watch this today on lunch break. :) To be frank, I'm not even a Vue user, but Vite looks truly awesome. I love that popular framework authors are taking the time to make their build tools framework-agnostic (also see, wmr by the Preact guys).

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.