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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@liter/common-fetch

v1.0.0

Published

+ 提供最常用的 fetch 的使用方式

Downloads

4

Readme

common fetch

  • 提供最常用的 fetch 的使用方式

为什么用 fetch

传统的 ajax,一般使用回调方法,来处理响应、异常
写起来,很难看

为什么不用 axios

axios 提供 Promise 写法,而且兼容性更强
如果需要更强的兼容性,那当然应该使用 axios
但是如果你不需要很强的兼容性,而且想让项目更轻,则应该使用 fetch

common fetch 和 fetch 的区别?

fetch 作为一个基础的 api,应当提供全面的功能
这注定了 fetch 要提供很多“选项”,很多不常用的选项
当你面对一个全是按钮的桌面,而你每天几乎只使用一个按钮
为什么不把其他按钮遮住呢
生活应该简洁
这就是 common fetch 产生的原因

常用?

  • 数据交互格式 json
  • 不使用 http 状态码