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

texturepackerify

v0.1.7

Published

Command-line Texture Packer and Extractor.

Downloads

246

Readme

TexturePackerify

Command-line Texture Packer and Extractor.

Setup

  • Install Node.js
  • Install ImageMagick (check "Install legacy utilities" during installation.)
  • Navigate to your project root and run:
$ npm install texturepackerify

Build Atlases

Place images inside folders. Each folder will be packed to atlas:

src
├── atlas1
│  ├── img0.png
│  ├── img1.png
│  ├── ...
├── atlas2
│  ├── img12.png
│  ├── img13.png
│  ├── ...

Create pack.js:

const texturepackerify = require("texturepackerify");
const config = {
    url: "./src/", //path to atlases. Default: './'
    hashUrl: "./src/", //where to store 'hash.json'. Atlases path will be used as default
    scales: [1, 0.5] //output scales. Default: [1]
    force: false //force rebuild all atlases. By default packed atlases will be skipped
    defaultAtlasConfig: {
        //Override default atlas config: extraSpace, jpeg, extrude, pot, square, colorDepth, animations, spriteExtensions
    }
}
texturepackerify.pack(config, () => {
    console.log("done!");
});

Run:

$ node pack.js

Output:

src
├──...
│  atlas1.png
│  atlas1.json
│  atlas2.png
│  atlas2.json
│  hash.json
│  ...

Atlas Config

Each atlas can hold config.json with parameters:

  • "extraSpace" - space between texture frames. Default - 2
  • "border" - texture border. Default - 0
  • "jpeg" - output to jpeg. Default - false
  • "extrude" - add extra pixels in bounds. Default - false
  • "pot" - atlas size fixed to power of two. Default - true
  • "square" - atlas size fixed to square. Default - false
  • "colorDepth" - color depth for texture. Default - 8
  • "animations" - parse animations. Default - false
  • "spriteExtensions" - add extension to frame name. Default - true

Example

Place config.json in atlas folder:

src
├── atlas1
│  ├── img0.png
│  ├── ...
│  ├── config.json

config.json:

{
    "extraSpace": 0,
    "jpg": true,
    "extrude": true,
    "square": true,
    "colorDepth": 8
}

Extract

TexturePackerify can extract atlases. Place atlas.png and atlas.json to src folder. Create extract.js:

const texturepackerify = require("texturepackerify");
texturepackerify.extract({url:"./src/"}, ()=>{console.log("done!")});

Run:

$ node extract.js