After many hours of debugging, I've finally managed to find a way to draw gif frames in the terminal. iTerm also supports embedding gifs since version 2.9.20150512 but then the stopAnimation function would have to be a noop and be conditionally executed.

A slight problem I'm noticing is that the terminal can only handle so many characters being logged at once so it lags behind a bit.

Fixes: #2

cc @sindresorhus

This pull-request add support for optional width and height options, auto-adjusting size if any (or both) of them is not defined, also when running in Windows. It also unify the file and buffer functions, and fix two bugs related to alpha channel and when resized image has an odd number of rows.

How hard would it be to support rendering raw ArrayBuffer pixel data like how CanvasRenderingContext2D works in browsers? I'd also love to help with this support if I can get pointed in the right direction! :)

Hi @sindresorhus 😊

I have created a PR to scale images, as requested in #1.

Since I wanted to keep the aspect-ratio, I only introduced a single factor parameter, not separate options for width and height.

I hope you like the changes 😊

Cannot install I'm getting an error by npm-

npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm ERR! code ENOENT npm ERR! syscall spawn git npm ERR! path git npm ERR! errno -4058 npm ERR! enoent Error while executing: npm ERR! enoent undefined ls-remote -h -t ssh://[email protected]/notmasteryet/jpgjs.git npm ERR! enoent npm ERR! enoent npm ERR! enoent spawn git ENOENT npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in:

https://github.com/sindresorhus/terminal-image/blob/a659386d84576c645c69fb43e3517d4030223d66/index.js#L47

Both term-img and jimp accept as first parameter both a buffer of a filepath, so usage of readFIle() is superfluous and also add some limits...

Not sure why, but I get this error when I try to import the library:

internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:750:11)
    at Loader.resolve (internal/modules/esm/loader.js:85:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:51:40)
    at link (internal/modules/esm/module_job.js:50:36) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}```

Hi! I was wondering if there's a CommonJS version of this module for use in NodeJS? All my other modules are in CommonJS and if I set "type": "module" in my package.json it will break all the rest.

Thank you.

Are you interested to switch from Chalk to Colorette to reduce the bundle size?

https://bundlephobia.com/[email protected]

https://bundlephobia.com/[email protected]

Would be nice to have https://github.com/sindresorhus/terminal-image/pull/7 finished, but the PR submitter is not responding.

Looking for someone to finish that PR and address the PR feedback. Preserve the existing commits and just add new ones in a new PR>

Description This PR adds a new method for converting "ImageData" as described in #4

Changes

• Refactored render() function body into 2 smaller functions: scaleImage and renderImage
• Added new imageDataToImage() function for converting ImageData to a Jimp instance
• Added new export imageData()
• Updated README with imageData() method docs

Testing I created a new test case to cover the update, however, I think I could use some help identifying whether or not this method works as expected.

Additional Info Although the passed imageData provides RGBA pixel data, right now, this implementation will ignore the alpha channel. I want to get a few eyes on this before I dive in further into any specific issue.

Anyways, let me know what to change/fix @sindresorhus 👍

Fixes #4

Whenever I try to make it render a black and white image, it just prints a bunch of white, Any fix? My entire code is literally just this: const terminalImage = require('terminal-image'); (async () => { console.log(await terminalImage.file(frames/out20.png)); })();

Doing a quick test to see if I can use this with https://github.com/Automattic/cli-table ...

const terminalImage = require('terminal-image');
const Table = require('cli-table');

(async () => {
	const img = await terminalImage.file(process.argv[2], {width: 50, height: 50});

	const table = new Table({head: ['img', 'caption']});
	table.push([img, 'description #1'], [img, 'description #2']);
	console.log(table.toString());
})();

It works nicely in macOS native terminal:

But in iTerm 2 I'm getting a screen full of lines, like the table thinks the output is (much) larger than it is. Customizing row widths in cli-table doesn't seem to help. Any idea if this is something I could reasonably expect to work, or just incompatible with whatever special image rendering iTerm 2 has? Maybe related to #29? Thanks!

Ranger file manager (linux) can show images preview (via w3m as far as I know) a lot way better than terminal-image. Is that possible to get such quality? Ranger shows in terminal exactly the source quality of an image.