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

clopos.electron

v1.2.295

Published

1. Make sure you have node and npm installed 1.2 Install visual studio community edition 2. **npm install --global --production windows-build-tools --save-dev** // This will take some time. Run it once 3. **npm install** 4. Install typescript glob

Downloads

30

Readme

First time

  1. Make sure you have node and npm installed 1.2 Install visual studio community edition
  2. npm install --global --production windows-build-tools --save-dev // This will take some time. Run it once
  3. npm install
  4. Install typescript globally to have tsc cli available and run npm run compile
  5. npm run rebuild // Run it each time new module w/native dependencies is installed
  6. npm start

Building exe

  1. To build an exe npm run exe and look into new folder
  2. When you want to build an exe and have new dependencies for your electron app add them to the package.json inside dist/package.json . It's needed for electron exe builder to know what dependencies to install. It can't look into root directory package.json, because of some unwanted developer dependencies.

Printing for USB Devices

if you use usb as an adapter :

  • On Linux, you'll need libudev to build libusb.
  • On Ubuntu/Debian: sudo apt-get install build-essential libudev-dev.
  • On Windows, Use Zadig to install the WinUSB driver for your USB device

Otherwise you will get LIBUSB_ERROR_NOT_SUPPORTED when attempting to open devices.