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

lygrafmajik

v0.1.0

Published

GraphicsMagick wrapper for node.js

Downloads

3

Readme

lygrafmajik

GraphicsMagick wrapper for node.js

What's lygrafmajik ?

In fact, lygrafmajik is simple (not as the name I choose).

It's just a simple wrapper to the CLI of GraphicsMagick for Node.js.

Why don't you use the npm module for GraphicsMagick ?

I think the npm module for GraphicsMagick is really, really great.
But when dealing with big images on large websites, the processing time is way too big.

So I write an handler to deal with the CLI, but without control, without verification. You must use the documentation of GraphicsMagick to know what parameters to give to each methods.

Getting Started

Install the module with: npm install lygrafmajik

lgm = require('lygrafmajik');

lgm( "./from_file.jpg", "./to_file.jpg" )
    .convert
    .size( "100x100" )
    .strip()
    .interlace( "Line" )
    .geometry( "100x100^>" )
    .gravity( "Center" )
    .extent( "100x100" )
    .quality( 95 )
    .exec( function( oError ) {
        // do awesome things !
    } );

Documentation

After including the module and storing to a variable, initiate an lygrafmajik object by calling it :

It accept two parameters : source path and destination path.

lgm = require('lygrafmajik');
myImage = lgm( "./from_file.jpg", "./to_file.jpg" );

After that, you must precise the GraphicsMagick utility you want to use.

For now, two are supported : convert and identify.

myImage.convert;

Then, you can call all the options you want to use to treat your image.
Refer to the doc of convert and identify to know the usage.

myImage.strip();
myImage.geometry( "100x100^>" )
myImage.gravity( "Center" );

When all is set, you can call the exec method to let the magic happens. The optional callback function get three parameters :

  • error Error
  • stdout Buffer
  • stderr Buffer

Those are the three parameters of the child_process.exec's node.js command callback.

myImage.exec( function( oError ) {
    if( oError ) {
        // do less awesome things...
    }
} );

As each methods of lygrafmajik object returns itself, all the above methods can be chained, jQuery-style :

lgm = require('lygrafmajik');

myImage = lgm( "./from_file.jpg", "./to_file.jpg" )
    .convert
    .size( "100x100" )
    .strip()
    .interlace( "Line" )
    .geometry( "100x100^>" )
    .gravity( "Center" )
    .extent( "100x100" )
    .quality( 95 )
    .exec( function( oError ) {
        if( oError ) {
            // do less awesome things...
        }
    } );

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • 2014/01/03 : v0.1.0

License

Copyright (c) 2014 Leny
Licensed under the MIT license.

TODO

  • Writing Unit tests ;)