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

@setapp/setapp-button

v1.0.0

Published

Setapp button for vendors sites

Downloads

6

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

khvalakhvalanas1k-macpawnas1k-macpawwallwhitewallwhitesetapp-devsetapp-devdimamyhalmacpawdimamyhalmacpawsokyransokyranonikiienkoonikiienkolequanlequanspanchenkospanchenko

Keywords

Readme

Desktop-App-Helper

Contributing guide

  1. Create feature branch and perform changes.
  2. Push changes to the origin and create pull-request.
  3. After pull-request merging update local master.
  4. Bump version and add a tag (for example using npm version).
  5. Build module npm run build.
  6. Push changes to the origin.
  7. Publish new version to NPM.

Versioning rules

  • patch - new features and non-breaking fixes for existing ones. Does not require related projects updating
  • minor - breaking changes that require related projects updating
  • major - reserved for major updates

Testing in related projects

There is a way to test new version of desktop-app-helper without publishing it to NPM:

  1. Execute npm link inside desktop-app-helper project root.
  2. Execute npm link @macpaw/desktop-app-helper inside related project's root.
  3. Rebuild related project if needed.

Scripts

  • npm run lint - check code with eslint
  • npm run build - it will generate lib dir with ES4 files