npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@seo-solver/fetch

v0.1.0

Published

HTTP and content fetch pipeline for SEO Solver

Readme

@seo-solver/fetch

@seo-solver/fetch is the base fetch layer for the whole workspace. Use it when you want one stable way to fetch a page, normalize the response, and hand the result to extraction, comparison, or validation code.

Installation

pnpm add @seo-solver/fetch

What this package gives you

  • a simple fetchUrl() API for one-off requests
  • a reusable createFetcher() API when you want to keep a fetcher around
  • a structured fetch result that downstream packages already understand
  • structured fetch errors with stable error codes
  • an advanced surface for backend registration and shared retry execution

Simple API

If you just want to fetch a URL and work with a normalized result, use the root package.

import { fetchUrl } from '@seo-solver/fetch';

const result = await fetchUrl('https://example.com');

console.log(result.url);
console.log(result.statusCode);
console.log(result.resourceType);

The returned object is the same canonical fetch shape used by the rest of the seo-solver packages. If you want to reuse a fetcher instance, use createFetcher() rather than instantiating an implementation class directly.

Advanced API

The application uses the advanced surface when it needs backend selection and shared retry behavior rather than a one-off fetch helper.

import { createFetcher } from '@seo-solver/fetch';
import {
  createSharedRetryExecutor,
  registerBackend,
  registerNativeBackend,
  resolveBackend,
} from '@seo-solver/fetch/advanced';

registerNativeBackend();

registerBackend('custom', async () => ({
  createFetcher(config) {
    return createFetcher(config);
  },
}));

const backend = await resolveBackend('native');
const fetcher = backend.createFetcher();

Reach for @seo-solver/fetch/advanced when you are wiring backends, retries, or orchestration. Backend registration is explicit: importing the module does not register native by itself.

Error model

Fetch failures use a structured contract with stable code values and retryability hints. That makes it safer to branch on fetch errors without coupling your code to a backend-specific error class.

Related docs and examples