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

@inho-team/project-checks

v0.1.1

Published

Production bundle and build input checks

Vulnerabilities

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

Links

Git

Maintainers

kjsung0129kjsung0129

Keywords

Readme

@inho-team/project-checks

운영 빌드의 JavaScript sourcemap에서 금지된 소스 경로를 찾고, 지정한 진입 파일의 바이트 크기를 확인합니다. 빌드 입력의 해시를 기록하거나 비교할 수 있습니다.

{
  "outputDir": "dist/client",
  "forbiddenSources": ["/mocks/", "/server/"],
  "entryFiles": ["assets/index.js"],
  "maxEntryBytes": 150000
}
inho-checks bundle bundle-check.json
inho-checks fingerprint:write dist/build-inputs.json src package.json
inho-checks fingerprint:check dist/build-inputs.json

크기 예산과 금지 경로는 서비스가 정합니다. 금지 경로를 지정하면 모든 JavaScript 출력 파일에 대응하는 sourcemap이 있어야 합니다. 검사기는 sourcemap의 sourceRoot와 sources를 함께 확인하며, 누락된 sourcemap이 있으면 검사를 실패시킵니다.