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

@naverpay/publint

v0.0.2

Published

@naverpay/publint is a specialized tool for verifying and linting npm package structure and `package.json` files, tailored specifically for NaverPay frontend developers. It ensures that packages meet both general npm standards and NaverPay's internal best

Downloads

77

Readme

@naverpay/publint

@naverpay/publint is a specialized tool for verifying and linting npm package structure and package.json files, tailored specifically for NaverPay frontend developers. It ensures that packages meet both general npm standards and NaverPay's internal best practices for modern JavaScript and TypeScript projects.

Features

  • Validates the structure and content of package.json
  • Enforces NaverPay-specific frontend development rules
  • Supports TypeScript projects
  • Verifies package types (regular, module, or dual)
  • Checks the exports field
  • Ensures presence of required fields
  • Validates output paths
  • Provides a user-friendly CLI interface

NaverPay Frontend Guidelines

This tool incorporates NaverPay's internal frontend development guidelines, ensuring that all packages published by the team maintain consistent quality and structure. Some of the NaverPay-specific checks include:

  • Adherence to NaverPay's naming conventions
  • Verification of required NaverPay-specific fields in package.json
  • Checks for compliance with NaverPay's code structuring rules
  • Validation of dependencies against NaverPay's approved list

By using @naverpay/publint, developers can ensure their packages are compliant with team standards before publication.

Installation

You can install @naverpay/publint globally:

npm install -g @naverpay/publint

Or use it directly with npx without installing:

npx @naverpay/publint

Usage

If installed globally, you can use publint directly in your project directory:

publint

Or specify a custom directory:

publint ./my-project

Using npx (without global installation):

npx @naverpay/publint

Or with a custom directory:

npx @naverpay/publint ./my-project

What it checks

  • Presence and validity of package.json
  • Correct structure of the exports field
  • Presence of required fields in package.json, including NaverPay-specific fields
  • Package type (regular, module, or dual) and corresponding structure
  • TypeScript configuration and type definition files (if applicable)
  • Validity of output paths defined in the exports field
  • Compliance with NaverPay frontend development guidelines

Output

The tool will provide detailed feedback on the verification process, including any errors or warnings encountered during the checks. It will specifically highlight any deviations from NaverPay's internal standards.

Contributing

Contributions are welcome from NaverPay team members! Please ensure you're familiar with our internal development guidelines before submitting a Pull Request.

License

MIT License

Acknowledgements

This project was inspired by publint, created by Bjorn Lu. We appreciate their work in improving the npm package ecosystem. @naverpay/publint builds upon this foundation to meet the specific needs of the NaverPay frontend development team.