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

simple_blitline_node

v2.3.4

Published

Thin wrapper around the Blitline service. No rocket science here, just a helper wrapper

Downloads

107,296

Readme

simple_blitline_node

This is a EVEN THINNER wrapper around the Blitline.com web service. Blitline provides a web based image processing service.

You must first have a Blitline.com account to successfully use the gem. You can obtain one (free and without obligation, not even an email address) by going to http://www.blitline.com

Once you have your account, you will need to find you ACCOUNT_ID which you can get by logging in and clicking on the Account tab.

For your node project, simply npm install it

$ npm install simple_blitline_node

Once installed, you can try the following code in your NodeJS app:


    var Blitline = require('simple_blitline_node');
    var nodeutil = require('util');
    var blitline = new Blitline();
    
    /* Replace MY_APP_ID with your Blitline applicationID */
    var applicationID = "MY_APP_ID";

    blitline.addJob({
        "application_id": applicationID,
        "src":"http://cdn.blitline.com/filters/boys.jpeg",
        "functions":[
            {
                "name":"resize_to_fit",
                "params":{
                    "width":100
                },
                "save":{
                    "image_identifier":"MY_CLIENT_ID"
                }
            }
        ]
    });

    var promise = blitline.postJobs();
    promise.then(function(data) {
        console.log(data);
    });

And you will get JSON back describing where the resulting image will be located There are many more things you can do with images (including pushing them to your own S3 buckets).

You can find documentation about Blitline.com and it's services by following the links in the Further reading section below

Further reading:

  • (Quickstart)[http://www.blitline.com/docs/quickstart]
  • (Blitline Blog)[http://blitline.tumblr.com]

== Contributing to blitline

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.