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

@wisdomgarden/mobile-assets

v0.0.79

Published

host mobile assets

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

resizable-humanresizable-humanchenzhiyuan01chenzhiyuan01chenyunjie1chenyunjie1peixinpeixindengzhirong93dengzhirong93zihningzihningyaoxiangyiyaoxiangyi

Keywords

Readme

Update assets flow

Update version info

I. Sync version file files

  • In Project mobile-assistant, prepare the preliminary work according to readme.md.
  • You should clone mobile-assistant into the same directory as the current project.
  • use bash ./scripts/sync_version_files.sh to sync latest file

II. upgrade package mobile-assets version

  1. ues git diff to check the changed files
  2. then commit all files git commit -m "update version file"
  3. node scripts/upgrade_version.js increase current project version number and add new tag
  4. git push && git push --tags push to GitHub, and Github Action publish it to npm @wisdomgarden/mobile-assets

III. refresh cdn

  1. after about 10 minutes, check jsDeliver package data util latest tag is same as package.json.version then bash scripts/refresh_cdn.sh refresh json file cdn cache
  2. preview release note. local use live server ./preview-release.html or Online from GitHub Pages

if update other file, edit refresh_cdn.sh, then run bash scripts/refresh_cdn.sh refresh it.

Update privacy policy

Privacy-policy / user-agreement files live in app-legal/. Edit them there, then publish via II. Keep the whole set in that folder — pages load policy-common.* / marked-4.0.1.min.js and fetch their *-info.json / *-<lang>.md by relative path.

  • Root-level copies are legacy duplicates for already-released apps still using the root URLs; edit them in sync, and delete once those app versions are retired.
  • China app-market review snapshots: see app-legal/store-review/.