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

@omniaz/vue-component-library

v0.6.18

Published

- get the code of the project from repository, - make changes to package code if needed, - run `npm adduser` to login to your npm account (create it if needed), - change `version` in `package.json`, - run `npm run build`, - execute `npm publish

Downloads

1,014

Readme

Development:

  • get the code of the project from repository,
  • make changes to package code if needed,
  • run npm adduser to login to your npm account (create it if needed),
  • change version in package.json,
  • run npm run build,
  • execute npm publish --access public to publish new version of the package.

Testing local version of the package in other project:

  • execute npm link in this package folder to create global link to local package version (only once),
  • execute npm link @omniaz/vue-component-library in other project (e.g. FMCG platform) to use local version of the package instead of remote one (every time, to test changes),
  • you may need to delete package-lock.json in other project and run npm run dev again to see changes.

Reverting to package from npm repository

  • just run npm install or npm update in the other project to revert back to using package version from node_modules.