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

base-webpack-xfq

v1.0.0

Published

> 提取 CDN 文件

Downloads

2

Readme

公共文件的拆分

提取 CDN 文件

html-webpack-externals-plugin

公共文件缓存

optimization

构建错误

优化构建时的日志展示 friendly-errors-webpack-plugin

冒烟测试

开发人员预先测试功能是否可用,再给到运维人员测试(文件类测试)

需要:模板项目、测试用例(mocha)

主要功能,在给到测试人员的时候,自己先进行测试,文件

单元测试

代码类测试

> 单元测试可以对业务代码进行测试吗?和平时自己本地运行调试有什么本质上的区别吗?

单元测试可以对业务代码进行测试,我们团队针对核心业务会做单元测试和端对端测试。单测更加适合通用组件和基础模块。

和本地调试的区别:本地调试是黑盒,颗粒度较粗,单测是白盒,颗粒度更细。

另外单侧可以覆盖到具体的代码,比如某段代码只有特定的情况才会执行。单测也是一个衡量项目质量很好的手段,每次需求迭代都可以通过单测保证基础的逻辑不受到影响。

> 冒烟测试可以直接运行构建看是否成功,单元测试一项一项测是不是比冒烟麻烦很多,单元测试的优势是什么相对于冒烟?

单元测试颗粒度更细,是白盒,需要针对具体的代码逻辑分支进行测试用例编写。冒烟测试只是关注最基本的功能是否ok,比如构建是否成功,是否有资源生成出来,也是一个黑盒的过程。


需要了解 前端测试方向

持续集成

接入 Travis CI

将有权限的 git 项目加入到 travis CI 中

通过 .travis.yml 文件,执行一个持续集成的脚本

发布到 npm