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

@giosg/pub-sdk

v1.1.0

Published

TypeScript interfaces for Giosg Pub

Downloads

114

Readme

Giosg Pub SDK and interfaces

This folder should contain some kind of ts interfaces

Publishing

Before publishing, remember to consider the effects your changes have for our users. See semantic versioning.

Script npm run prepare will run before publishing automatically. Make sure you are in the giosg_pub/interfaces folder when you are trying to publish the package. Don`t publish something else by accident. If you did, unpublish it within 72 hours. For publishing, you need access to giosg organization in npm. You can request that from one of the organization admins or request them to publish the package.

  1. Update CHANGELOG.md, update package version (e.g. with npm --no-git-tag-version version <major|minor|patch>), and commit.
  2. Create pull request.
  3. Request a review from another experienced developer.
  4. Merge the pull request after approval and passed tests.
  5. Pull master locally.
  6. Login to npm with npm login --scope=giosg. You will be prompted for credentials.
  7. Build version with npm run prepare command.
  8. Publish the package with: npm publish --access public. --access public flag is mandatory because organization packages default to restricted.
  9. Create a new tag on the latest commit on master branch git tag vX.Y.Z X.Y.Z being the published version.
  10. Push the tag to remote git push --tags.

TODO:

  • add lint
  • add grammarchek