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

@dloizides/e2e-helpers

v1.0.1

Published

Shared Playwright E2E building blocks for the estate's two-tier (@api/@ui) suites — reachability, ROPC realm tokens, auth headers, health polling, multipart CSV, username/email derivation.

Readme

@dloizides/e2e-helpers

Shared building blocks for the estate's two-tier (@api / @ui) Playwright E2E suites. Generic, product-agnostic helpers extracted from the per-product *-helpers.ts files so a new product's E2E is a thin wrapper, not another copy-paste.

@playwright/test is a peer dependency — the consuming E2E suite provides it.

Install

npm i -D @dloizides/e2e-helpers

API

| Helper | Purpose | |--------|---------| | resolveBaseUrl(envVar, fallback) | env-configurable base URL (trailing slashes trimmed) | | tryRequest(request, baseUrl, path, opts?) | request that returns null on transport failure → test.skip gracefully | | bearer(token) / jsonAuth(token) | auth headers (GET/DELETE vs JSON body) | | resolveKeycloakBaseUrl() | derive KC base from KEYCLOAK_URL / KEYCLOAK_ISSUER | | getRealmToken(realm, opts) | ROPC access token for a realm; null when unconfigured | | waitForHealthy(request, baseUrl, path, timeout?) | poll a health path until 2xx | | deriveUsername(email) / uniqueEmail(prefix?) | Keycloak-legal username + unique register email | | csvMultipart(csv, filename?) | Playwright multipart body for a CSV upload (file field) |

Example (@api spec)

import { expect, test } from '@playwright/test';
import { resolveBaseUrl, tryRequest } from '@dloizides/e2e-helpers';

const BASE = resolveBaseUrl('AML_API_URL', 'https://aml-screening.dloizides.com');

test('rejects an unauthenticated screening @aml-api', async ({ request }) => {
  const r = await tryRequest(request, BASE, '/v1/screenings/check', { method: 'POST', data: { fullName: 'x' } });
  if (!r) { test.skip(true, `service not reachable at ${BASE}`); return; }
  expect([401, 403]).toContain(r.response.status());
});

Convention

Every network helper returns null/false on failure so specs skip, not fail where the target isn't reachable — safe on the dev PC, meaningful on the nightly in-cluster runner.