The file command uses sophisticated methods to identify file types from their name and contents. This library brings that powerful capability to javascript projects in an efficient and integrated way.
The projects directly uses the native C implementation of libmagic, transpiled to Web Assembly using emscripten. The result is a close to native performance for file type identification, portable across any platform that has node.js.
- Get a descriptive string of the file contents
- Get the mime type and mime encoding of a file
- Optimized loading of the magic file for multiple calls to the API or uses from multiple threads (e.g. WebWorker)
NOTE: file system access is required and therefore the module is only useful in node.js environment. There is possibility though to enhance it to provide content identification using buffers and with the magic file preloaded in emscripten virtual filesystem (not implemented for now).
import * as fs from 'fs';
import * as path from 'path';
import { FileMagic, MagicFlags } from '@npcz/magic';
// Tell FileMagic where to find the magic.mgc file
FileMagic.magicFile = require.resolve('@npcz/magic/dist/magic.mgc');
// We can only use MAGIC_PRESERVE_ATIME on operating systems that support
// it and that includes OS X for example. It's a good practice as we don't
// want to change the last access time because we are just checking the file
// contents type
if (process.platform === 'darwin' || process.platform === 'linux') {
FileMagic.defaultFlags = MagicFlags.MAGIC_PRESERVE_ATIME;
}
// Get the single instance of FileMagic and work with it
FileMagic.getInstance()
.then((magic: FileMagic) => {
// The version is a number with the left most digit being the major
// version and the other digits are the minor
const version = magic.version();
const major = ('' + version).charAt(0);
const minor = ('' + version).substr(1);
console.log(`Using magic version: ${major}.${minor}`);
// We can call the detection methods
const files = fs.readdirSync('.');
console.log(`${files.length} files to check`);
files.forEach((file) => {
console.log(
file,
' : ',
magic.detect(file, magic.flags | MagicFlags.MAGIC_MIME)
);
console.log(file, ' : ', magic.detect(file));
});
// When we are done, close
FileMagic.close();
})
.catch((err: Error) => {
console.error(err);
// when the initialization fails, FileMagic already cleans up, but
// there is no harm in getting used to always close when no longer
// needed.
FileMagic.close();
});
import * as fs from 'fs';
import { MagicBindingModule, MagicBindingInterface } from '@npcz/magic';
const createBindingModule = require('@npcz/magic/dist/magic-js');
const magicFile = require.resolve('@npcz/magic/dist/magic.mgc');
createBindingModule().then((binding: MagicBindingModule) => {
console.log(binding.MagicBinding);
console.log(`Magic version : ${binding.MagicBinding.version()}`);
// We can only use MAGIC_PRESERVE_ATIME on operating systems that support
// it and that includes OS X for example. It's a good practice as we don't
// want to change the last access time because we are just checking the file
// contents type
let flags = 0;
if (process.platform === 'darwin' || process.platform === 'linux') {
flags = binding.MAGIC_PRESERVE_ATIME;
}
if (-1 === binding.MagicBinding.init(magicFile, flags)) {
console.error('Initialization failed!');
return;
}
const magic: MagicBindingInterface = new binding.MagicBinding();
const files = fs.readdirSync('.');
console.log(`${files.length} files to check`);
files.forEach((file) => {
console.log(
file,
' : ',
magic.detect(file, binding.MagicBinding.flags() | binding.MAGIC_MIME)
);
console.log(file, ' : ', magic.detect(file, -1));
});
binding.MagicBinding.destroy();
});
npm i @npcz/magic
yarn add @npcz/magic
To build the module from source:
cd magic
yarn install
yarn link
yarn link "@npcz/magic"
yarn build
yarn test
yarn example:raw
git clone https://github.com/npcz/magic.git
yarn example:magic
The build uses docker to reduce the hassle of platform specific things when building libmagic. Setting up docker varies between platforms, refer to the official docker documentation.
It's important to do the yarn link
steps so that the test cases and examples
use the local module while still referring to it as if it were installed.
Pull requests, bug reports, enhancement suggestions etc... are welcome at the github repository.
- This file command (and magic file) was originally written by Ian Darwin (who still contributes occasionally) and is now maintained by a group of developers lead by Christos Zoulas.
- Piotr Paczkowski for the emscripten docker images.
- The emscripten project.
This project is licensed under the BSD-3-Clause License