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

neysla

v4.0.4

Published

Promise based HTTP RESTful API resources modeler for browser and Node 18+

Readme

Neysla

CI codecov NPM Node version

Documentación

  • Aquí puedes acceder a la documentación de Neysla.

Migración de v3 a v4

Manejo de errores

// v3
const result = neysla.init(config);
if (!result) {
  /* error */
}

// v4
try {
  const result = await neysla.init(config);
} catch (err) {
  // err es un TypeError con el mensaje de error
}

Headers de respuesta

// v3 (XHR — case-sensitive)
response.headers["Content-Type"];

// v4 (fetch API — siempre lowercase)
response.headers["content-type"];

setModel() errores

// v3
const model = service.setModel(2);
if (!model) {
  /* error */
}

// v4
try {
  const model = service.setModel(2);
} catch (err) {
  // err es un TypeError
}

Tests manuales

Los tests manuales se encuentran en test/manual/. Requieren un build previo:

npm run build

| Archivo | Descripción | Comando | | ---------------------- | ------------------ | -------------------------------------- | | test/manual/esm.mjs | Node.js — ESM | node test/manual/esm.mjs | | test/manual/cjs.cjs | Node.js — CJS | node test/manual/cjs.cjs | | test/manual/cdn.html | Browser — IIFE/CDN | Servir localmente, abrir en el browser |

Para el test de browser puedes usar cualquier servidor local, por ejemplo:

npx serve .
# Abrir: http://localhost:3000/test/manual/cdn.html

Release

Para publicar una nueva versión a npm via GitHub Actions:

# 1. Actualizar version en package.json
npm version patch   # o minor / major

# 2. Empujar el commit y el tag
git push origin master
git push origin --tags

El workflow .github/workflows/publish.yml se dispara automáticamente con cualquier tag v* y publica a npm via Trusted Publishing (sin token).

Autor

Licencia

Licencia MIT.

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Documentation

  • Here you can access Neysla's documentation.

Migration from v3 to v4

Error handling

// v3
const result = neysla.init(config);
if (!result) {
  /* error */
}

// v4
try {
  const result = await neysla.init(config);
} catch (err) {
  // err is a TypeError with the error message
}

Response headers

// v3 (XHR — case-sensitive)
response.headers["Content-Type"];

// v4 (fetch API — always lowercase)
response.headers["content-type"];

Manual tests

Manual tests are located in test/manual/. They require a build first:

npm run build

| File | Description | Command | | ---------------------- | ------------------ | --------------------------------- | | test/manual/esm.mjs | Node.js — ESM | node test/manual/esm.mjs | | test/manual/cjs.cjs | Node.js — CJS | node test/manual/cjs.cjs | | test/manual/cdn.html | Browser — IIFE/CDN | Serve locally and open in browser |

For the browser test you can use any local server, e.g.:

npx serve .
# Open: http://localhost:3000/test/manual/cdn.html

Release

To publish a new version to npm via GitHub Actions:

# 1. Update version in package.json
npm version patch   # or minor / major

# 2. Push the commit and the tag
git push origin master
git push origin --tags

The .github/workflows/publish.yml workflow triggers automatically on any v* tag and publishes to npm via Trusted Publishing (no token required).

Author

License

MIT License.