registry VS flow-pipeline

More important than the namespace is who published the package. I'm more inclined to trust an individual I know who takes security than a namespace that may change hands.

NPM exposes that info in the _npmUser field: https://github.com/npm/registry/blob/master/docs/REGISTRY-AP.... That gives "name" (NPM username) and email.

While there are thousands of packages, I bet there's a much smaller number of publishers to worry about.

I can't find anything about it in their docs. https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md

https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md here are the docs. I was getting 122ms responses instead of 9000 on the old one.

My first instinct was to work with the public API of the npm registry. This sounds like a very good idea, but you will soon run into a set of problems (cache, private registry etc..).

There is no need to obtain an API key or token for querying NPM registry API. For the dashboard, I use only the endpoint that provides the data about a package downloads count - https://api.npmjs.org/downloads/. You can read more about it here.

While many people regularly use npm's website to discover packages, only a few know that npm also provides a public REST API accessible at registry.npmjs.org.

Or roll your own, docs here: https://github.com/npm/registry/blob/master/docs/download-counts.md

Many Thanks to Cloudflare and dev.to for giving us this opportunity.

Unlike other providers in this list, Cloudflare is not just a serverless database platform. Instead, it’s a cloud connectivity platform that provides several web services. It’s one of the world's largest networks and serves 55 million HTTP requests per second.

Using a Content Delivery Networks (CDNs) such as Cloudflare, can help absorb large amounts of traffic and mitigate the impact of DoS attacks.

When a user requests a webpage, the CDN delivers the content from the nearest server to the user. As a result, the loading times are faster since the data has to travel a shorter distance. CDNs offer endless benefits like reduced bandwidth usage, scalability, increased reliability, and more. Some well-known CDNs include Cloudflare, Amazon CloudFront, Akamai, and Fastly. They offer several features that help reduce web page sizes and make websites run better.

Cloudflare

Cloudflare offers low/no markup domain name registration with a free DNS service. This will virtually always be your cheapest option for domain name renewals. They don't list prices for all TLDs upfront, so use this list to get your best estimate.

Our site used Cloudflare to handle all our DNS needs. Cloudfare has a number of rewrite options but as we needed to make a decision based on a) the URL path and b) rewriting to a specific domain, the only option (as a non enterprise customer) was to use Cloudflare workers (via worker routes).

Add Cloudflare Cahce & Protection

Cloudflare is a cloud-provider, most-known for their CDN, offering several services to build cloud applications. Among them, Cloudflare Workers is a serverless service that allows you to run serverless functions at edge (like Lambda@Edge if you are an AWS user). This means that your code runs closer to end-users, resulting in blazing fast response times.