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

jonasbroms-www

v1.13.1

Published

Jonas Bröms official website built with Gatsby, Novela Theme & Semantic-Release. Tested in Travis-CI & deployed to Netlify.

Readme

Jonas Bröms official website & blog

Travis Status

Netlify Status

Dependencies

You need to have these CLI and dependencies in order to download and install everything without a clitch.

| Logo | Name | |-----------------------------------------------------------------------|-----------------------------------------| | Homebrew Logo | Homebrew | | | NVM | | NodeJS Logo | NodeJS | | Yarn Logo | Yarn | | GatsbyJS Logo | GatsbyJS | | Netlify Logo | Netlifiy | | Travis Logo | Travis-CI | | Semantic-Release Logo | Semantic-Release |

Quick start

Download

Navigate the a directory on your computer were you are working on sites and run this command:

git clone https://github.com/bromso/jonasbroms-www.git

Install

Navigate the site’s directory and run this command.

yarn

Start developing

Navigate the site’s directory and start it up.

yarn develop

Open the source code and start editing!**

| Name | Local | URL | |-----------|----------------------------------|--------------------| | Website | http://localhost:8000 | www.jonasbroms.com | | GraphQL | http://localhost:8000/___graphql | | | | | |

Contribution

Submitting changes

If this is the first time you are contributing to an Open-Source project we would really appreciate if you would read the Open-Source.guide before committing.

Please send a GitHub Pull Request to Odduse with a clear list of what you've done (read more about pull requests). We can always use more test coverage. Please follow our coding conventions (below) and make sure all of your commits are atomic (one feature per commit).

Semantic Versioning (Semver)

For transparency into our release cycle and in striving to maintain backward compatibility, Odduse is maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we adhere to those rules whenever possible.

Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this:

$ git commit -m "A brief summary of the commit
>
> A paragraph describing what changed and its impact."

| Type | Explanation | Semver (eg. 1.0.0) | Git Message Example | |-----------------|----------------------------------------------------------------|--------------------|--------------------------------------------------|
| fix | A bug fix | x.x.1 | fix: update package.json | | feat | A new feature | x.1.x | feat: add new eslint to package.json | | BREAKING CHANGE | A major change | 1.x.x | BREAKING CHANGE: upgrade to strapi 3 & gatsby 3 | | docs | Documentation improvements | | docs: update README.md | | style | Changes made white-space, formatting, missing semi-colons, etc | | style: add styles in breadcrumb component | | refactor | A code change that neither fixes a bug nor adds a feature | | refactor: fixed better intendation in index.html | | perf | Performance improvements | | perf: add tree-shaking to webpack | | test | Add missing tests | | test: add test to .travis.yml | | chore | Changes the build process | | chore: update .travis.yml & netlify.toml |

See the Releases section of our GitHub project for CHANGELOG for each release version of Odduse projects.

Editor preferences

Editor preferences are available in the editor config file for easy use in common text editors. Read more and download plugins at Editorconfig.

Coding conventions

Thanks in advance, Jonas Bröms, founder & Creative Director of Odduse