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

@homex/knowledge-types

v2.79.0

Published

TypeScript types for the Knowledge API

Downloads

437

Readme

semantic-release

📦 npm

@homex/knowledge-types

🛠 Getting started

  1. Clone the repository

    Note: Please make sure you are on the desired node version before starting any development. If you are using nvm, you can do the following:

    nvm install
    nvm use
  2. Install dependencies:

    npm install

👨‍💻 Development

  1. Perform desire changes in appropriate interface.

  2. Make sure code compiles and passes all ESlint rules:

    # Build
    npm run build
    
    # Lint validation
    npm run lint:fix
  3. Ready for PR ? Make sure your commit message is prefixed with one of this:

    | Commit message | Release type | | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------: | | fix(pencil): stop graphite breaking when too much pressure applied | ~~Patch~~ Fix Release | | feat(pencil): add 'graphiteWidth' option | ~~Minor~~ Feature Release | | perf(pencil): remove graphiteWidth option BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reasons. | ~~Major~~ Breaking Release |


    Once PR approved and gets merged to master, semantic release will take care of releasing next version of npm.