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 🙏

© 2026 – Pkg Stats / Ryan Hefner

pickly-posts-client

v1.1.0

Published

- this project to create npm library for pickly posts client. This client is generated using open api tools based off the openAPI defenitions for the posts api.

Readme

purpose

  • this project to create npm library for pickly posts client. This client is generated using open api tools based off the openAPI defenitions for the posts api.

Build prerequisits

  • inialize project

    1. run git init
    2. run yarn init in the root directory
    3. In package.json:
      • "name": "PACKAGE-NAME"
      • "repository": { "type": "git", "url": "https://github.com/Sahl-A/posts_client" }
      • "main": "lib/index.js"
  • semantic-release

    1. Documentation: https://semantic-release.gitbook.io/semantic-release/v/beta/
    2. create github token: https://github.com/semantic-release/github
    3. Add the generated token as a secret in the github repo with name GH_TOKEN
    4. yarn add semantic-release-cli --dev
    5. in the root directory: npx semantic-release-cli setup and answer the questions and provide the github token and choose github actions as our CI
    6. Once finished, it will add changes to package.json, e.g, add semantic release script, add it to dependencies, convert the repository url to https
    7. Add the CI configuration in release.yaml inside .github/workflows.
      • make sure to add GH_TOKEN & NPM_TOKEN as environment variables. The NPM_TOKEN will be added to the repo secrets automatically when running the CI action
      • make sure to enable the npm package to work with github CI: -- https://github.blog/changelog/2020-10-02-npm-automation-tokens/
    8. Add the following configuration in releaserc.yaml in project root directory:
    branches:
    - main
  • commitizen

    1. Add commitizen locally: yarn add commitizen --dev
    2. Initialize the conventional changelog adapter: npx commitizen init cz-conventional-changelog --save-dev --save-exact
    3. The above command added cz-conventional-changelog package and added it to dependencies and added its configuration to package.json
    4. For the sake of consistency, remove the config of commitizen added by the above command from package.json and add the following in .czrc:
    {
    "path": "cz-conventional-changelog"
    }
    1. The command npx commitizen init cz-conventional-changelog --save-dev --save-exact ran using npm and added package-lock.json. Since we work with yarn, we will run yarn to update the yarn.lock file, then remove package-lock.json
    2. add "commit": "cz" in scripts in package.json
    3. run yarn commit, it will open a dialoge to fullfill.
    4. Read more about the commit conventions:
      1. https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-format
      2. https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#

Buisness logic prerequisits

  • openAPI definitions file

    • add post.openApi.yml file in the root directory
  • openapi-generator-cli

    1. if not installed: sudo yarn global add @openapitools/openapi-generator-cli
    2. after installation run the following in root path: openapi-generator-cli generate -g typescript-axios -i OPENAPI_FILE.yaml -o lib/
  • axios

    1. yarn add axios
  • typescript

    1. if typescript is not installed: yarn global add typescript
    2. in project root directory tsc --init
    3. In the created tsconfig.json uncomment the following keys:
      • moduleResolution: "node"
      • declaration: true
      • sourceMap: true
      • target: "ESNext"
    4. in project root directory tsc --build
    5. in package.json add "main": "lib/index.js"