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

@rentouch/pi-components

v1.1.0

Published

Frontend components to be shared between vue applications

Downloads

12

Readme

PI Components

Component library to share custom components between frontend projects.

Install as dependency in your project

npm install @rentouch/pi-components

Updating this package in registry

Before publishing the new version you can install your updated package locally first to try it out. Let’s imagine following folder structure:

├── pi-web
├── pi-components

You can install the pi-components npm package from a folder like this:

# while being inside pi-web folder
npm install ../pi-components --install-links

When you made significant changes and you want to update your package in registry do the following:

  1. Checkout your feature branch from master.

  2. Commit your changes to your feature branch:

    git commit -m "Your changes"

  3. Specify new version (semver) with:

    npm version <newversion> -m "Bump version to X.Y.Z"

  4. Push automatically created tag while being on your feature branch:

    git push --follow-tags

  5. Create a PR from your feature branch against the master branch.

  6. Assign PR for review, after a successful merge to master, the CI will build and push the package to the npm repository.

Semantic Versioning

When deciding which version to use consider following:

| Code status | Stage | Rule | Example version | |:------------------------------------------|:--------------|:-------------------------------------------------------------------|:---------------:| | First release | New product | Start with 1.0.0 | 1.0.0 | | Backward compatible bug fixes | Patch release | Increment the third digit | 1.0.1 | | Backward compatible new features | Minor release | Increment the middle digit and reset last digit to zero | 1.1.0 | | Changes that break backward compatibility | Major release | Increment the first digit and reset middle and last digits to zero | 2.0.0 |

You can specify which update types your package can accept from dependencies in your projects's package.json file.

For example, to specify acceptable version ranges up to 1.0.4, use the following syntax:

Patch releases: 1.0 or 1.0.x or ~1.0.4
Minor releases: 1 or 1.x or ^1.0.4
Major releases: * or x

Testing

Run tests with:

npm run test

Styleguide

Start with:

npm run styleguide

which will host components on http://localhost:6060.