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

@omcfe/ufe-dev-dependencies

v0.0.13

Published

UFE Dev Dependencies

Downloads

7

Readme

UFE DEV Dependencies

About

This project is used for pulling UFE dev dependencies.

pipeline status coverage report

How to

Clone the project from git, then run npm i, then npm run update. It will try to get the latest dependencies and modify package.json accordingly. If there are changes, you should add and comit the package.json file.

A new release can be done by running npm version patch|minor|major. It will try and isntall the dependencies, and, if everything is good, it will create a new git tag and push everything to the git remote.

A special reelase pipeline will then be triggered for the newly created tag, and it will

Ex:

npm i
npm run update
npm commit -am 'Updated dependencies'
npm version patch