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

@stevebartmoss/neofetch

v1.2.3

Published

wraper de fetch para hacer mas simple el uso de la api nativa de js `fetch`

Downloads

5

Readme

Neofetch

wraper de fetch para hacer mas simple el uso de la api nativa de js fetch

Parametros

Neofetch.get(url,options)

url: Es la url a la que queremos mandar la peticion, en el caso de peticiones GET o DELETE no es necesario concantener las parameros

options: Es un objeto que espera tener la siguiente forma

{
  body: {},
  paramms: [{key: id, value: 1}],
  headers: {},
  optiosn: {}
}
  • body: Representa el cuerpo de la peticion en los tipos POST, PUT o PATCH se puede mandar como un objeto normal, internamente ya se hace el stringify

  • params: Es un arreglo de objetos de tipo key y value con el que se modifica el url de la peticion para que se manden correctamente

  • headers: Objeto que representa los encabezados que se quieren pasar en la peticion, ademas de los comunes que ya estan presentes en todas las peticiones

  • options: Objeto que representa opciones adicionales que se quieren argrea a la peticion

Interceptores

Se implemento el uso de interceptores para los errores al momento de realizar peticones http la forma de usarlo es la siguiente:

NeoFetch.interceptors.error.use((error) => {
  console.error("Error global:", error.status, error.message)
})

Manejo de errores

Se implemento la respuesta de una exception, de esta manera se puede usar un bloque try catch para el manejo de errores, se puede implementar de la siguiente manera

try{
  const { data } = await NeoFetch.get('/api/users')
} catch(error){
  console.error(`Error ${err.status}:`, err.data || err.message)
}

El objeto que se devuelte en la exception tiene el siguiente aspecto

error = {
    `HTTP ${response.status}: ${response.statusText}`,
    status: = response.status,
    data: data,
    url: swapurl,
}