I published my first npm package: filters

I published my first npm package: filters

Here is a problem that I am solving on almost every project: I need to have a generic way to manipulate data filtering options and pass them around. For example, I am building a CMS with a lot of data visualization (like tables and charts). Good data visualization should have a filtering ability. So users can filter the shit out of it and then send a link to the results.

I kind of tired of doing the same thing every time and want to do yarn add. And from today (yesterday, to be honest, but I did not have time to write this post), I can. And you can do it too.

npm i @barhamon/filters

Or, if you are a yarn user:

yarn add @barhamon/filters

I tried to do my best with read.me in the GitHub repo. So, for the sake of consistency, I will not repeat API here. But want to share my ideas of how I want to improve this package.

There is already a method to transform filters to MongoDB query so they can be used easily with Mongoose or just MongoDB driver. And I want to add integrations with other ORM/ODM like TypeORM. Also, since the backend can be written in different than JS languages, I want to write a port of this idea on your, my friend, favorite language (I will sooooooo write Rust crate for this. Soooooooooo write). And there should be examples of how to use it with different UI libraries. And better documentation. And investigate more space-efficient ways to communicate between the backend and frontend. And so on :)

I will gladly answer any questions or issues or accept pull requests.

How to iterate over the array in JavaScript and the root of all evil

How to iterate over the array in JavaScript and the root of all evil

benchmarking array methods vs for loop vs iterators vs generators

Redux is not bad

Redux is not bad

This is why you should use redux as a state manager for your app

First major refactoring

First major refactoring

the birthday of the Bar part of barhamon.com