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

@soltech/fluid-common

v0.9.3

Published

Fluid frontend, API and AI common interfaces & enums

Downloads

691

Readme

fluid-common

Fluid frontend and API commons

Contribution

  1. Make a change
  2. Bump the package version according to change severity
  3. Commit
  4. run npm run pub - it'll build the package, publish it to npm and push changes to github

But during the time of development, another version could have been deployed, without your change only available in your Pull Request. And you need to keep your branch updated with the main one. In that case, follow these steps:

  1. make sure your commons is up to date with main
  2. create a branch out of main and make your changes or update the branch of the PR
  3. bump the package version according to severity - that’s a bit tricky as that version may already be taken by a parallel work, so it’s worth checking other active branches or the npm itself
  4. commit and push the branch
  5. run npm run pub to publish the package
  6. refer to the package in your branch in another repo