filtrex VS hexpm

Filtrex

I was thinking of porting this library to Elixir. But first, I searched on hex.pm and Surprising. I found two packages that support merging tailwind classes: twix and tails

I often reference https://github.com/hexpm/hexpm which is the code behind hex.pm.

Feel free to take a look at the package manager and let me know if there are any libraries that you need that are missing. https://hex.pm/

I can assure you I'm not spending my time inventing new libraries. In the past 3 or so years of working in Elixir there have been maybe 2 or 3 cases where I was looking for a library and couldn't find a suitable one. Writing my own code to cover those cases took a few hours. This should hardly be a deal breaker for anyone if you take into account dozens, maybe even hundreds of hours the ecosystem could save you in the long run if your project is a good fit for it.

Before getting started you need to have both Elixir, the Hex package manager, the PostgreSQL relational database server and Node.js installed on your local computer to be able to follow through this guide.

We can then look at that function and see that ultimately it calls Supervisor.start_link(...) on a bunch of children. That means that one process's only job is to start up all those child processes and "supervise" them, meaning if any of them crash it will be notified and be able to handle that. I note that one of the processes runs the code in the module Hexpm.RepoBase which means it's in charge of managing database connections, and one runs the code in the module HexpmWeb.Endpoint which is the process in charge of managing the Phoenix side of things, handling incoming requests, spinning up new processes to handle each one, and directing them to the right controllers and stuff. Then there's a bunch of other modules listed, for things like rate limiting, billing reports, and other stuff. You can look in the codebase for those listed modules if you're interested, but the thing to note is that by putting the module name there, what happens is the supervisor will spawn a new process and run the start_link function of that module within that new process.

I was looking for a solution to run tests automatically every time I save any changes. The best way so far for me is the following hex package:

API server and website for Hex https://github.com/hexpm/hexpm

Dependency Current Latest Status bunt 0.2.0 0.2.0 Up-to-date cowlib 2.11.0 2.11.0 Up-to-date credo 1.6.1 1.6.3 Update possible db_connection 2.4.1 2.4.1 Up-to-date decimal 2.0.0 2.0.0 Up-to-date earmark_parser 1.4.19 1.4.20 Update possible postgrex 0.15.13 0.16.2 Update not possible To view the diffs in each available update, visit: https://hex.pm/l/AsY7q

Now it’s time to decide on a name for your package. In this guide I will be creating a new Ueberauth package. If you were to go on http://hex.pm and look at other Ueberauth packages, you notice there is a certain pattern followed. This will make the decision easy for us on what to call our Uberauth package that will implement the Patreon OAuth flow.

Go to the website https://hex.pm and search for the faker library to grab the latest version, so you can copy that to your mix config file, at the time of the making of this tutorial the latest version is 0.17.0, add the following to your project dependencies inside your mix.exs file: