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

@youkuohao/runtime

v0.71.4

Published

Downloads

4

Readme

Wroker Runtime

Get started

npm i

node example

Q&A

为什么生成单独的polyfill文件?

polyfill依赖了一些无法bundle的依赖包,这些依赖包要跟着cli安装。当cli安装在全局目录时, 在工作目录下运行dev依赖到polyfill,便会无法加载到依赖包(除非工作目录也安装了),所以runtime先执行, 再依赖polyfill(获取到全局目录下的路径),此时polyfill便可以依赖到依赖包。

如果polyfill实现零依赖打包,就不需要被抽离出去。

CLI会编译项目代码并让runtime去执行,执行的时候需要注册一些polyfill。 受限于node.js模块加载机制,polyfill注册的时候,依赖到的package需要安装 到项目所在路径。为了避免这个问题,不直接在runtime里注册polyfill,而是 先获取CLI下的polyfill文件路径,再require。这样polyfill依赖的package就 会从CLI路径下加载。

开源

如果开源的话,可以把polyfill/youkuohao分离出来,放到extension的injectScript里。

实际上fetchEvent也应该放到injectScript里。