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

letsenhance

v0.1.4

Published

Command line client for letsenhance.io - Enhance images in a directory

Downloads

10

Readme

letsenhance

Command line client for letsenhance.io - Enhance images in a directory

Install

npm i -g letsenhance

Or download one of the executables from the releases page

Usage:

Command line

letsenhance [options] email password /path/source /path/dest

Node

const Enhancer = require('letsenhance');

async function enhance() {
const enhancer = new Enhancer(options);
  let err = await enhancer.login(email, password);
  if (err) {
    return console.log('Login failed.');
  }

  err = await enhancer.enhanceDir(sourcePath, destPath);
  if (err) {
    return console.log(`Error while processing: ${err}`);
  }

  console.log('Processing complete!');
}

enhance();

Options:

--type string - JPEG (default) or PNG; PNG yields a larger file that maintains its quality across any subsequent alterations (jpeg does not);

--version string - magic (default, for photographs), boring (for everything else), color-enhance, tone-enhance;

--mode string - Auto (default); Auto is the only supported transformation mode at the moment;

--maxParallel number - 10 (default); how many files to process at a time; use a lower value if you encounter frequent issues;

--attempts number - 6 (default); how many times to re-attempt an operation after a 'soft' failure; the default value should suffice;

--progressInterval number - 15 (default); how many seconds to wait before checking a file's progress; use a greater value if an error message suggests it (e.g. 30 or higher);

--stopOnFirstFailedFile boolean - true (default) or false; stop the entire process on a 'hard' failure (used to prevent wasting available transformations);

Example with options:

letsenhance --type PNG --version boring --maxParallel 8 --progressInterval 30 [email protected] joespassword /path/source /path/dest

Notes:

Options must be placed before the email string.
If the paths or password contain spaces, use quotes: '/path to a dir' or "/path to another dir".
Make sure there are only images in the source path directory; other files will cause errors and eventually halt the process. Hidden files starting with '.' are ignored.
Don't use an option without a value, it may lead to unexpected results.