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

@illustra/p4exlib

v1.4.2

Published

External P4 UI References

Downloads

14

Readme

Introduction

Shared TypeScript modules, required by both P4 and the P4 Exernal Modules library

Getting Started

Installation: npm i @illustra/p4exlib

  1. Software dependencies
  2. Latest releases
  3. API references

Build and Test

Project based on the following article: https://itnext.io/step-by-step-building-and-publishing-an-npm-typescript-package-44fe7164964c

  • npm run lint

  • npm run format

  • npm run test - runs jest tests

  • npm run prepare - prepare will run both BEFORE the package is packed and published, and on local npm install. Perfect for running building the code

  • npm run preversion - runs before bumping a new package version. To be extra sure that we’re not bumping a version with bad code, why not run lint here as well?

  • npm run version - will run after a new version has been bumped. If your package has a git repository, like in our case, a commit and a new version-tag will be made every time you bump a new version. This command will run BEFORE the commit is made. One idea is to run the formatter here and so no ugly code will pass into the new version:

  • npm run postversion will run after the commit has been made. A perfect place for pushing the commit as well as the tag.

  • npm run publish --access restricted - publish to npm

Contribute

TODO: Explain how other users and developers can contribute to make your code better.

If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files: