file-type
- Version 22.0.0
- Published
- 135 kB
- 4 dependencies
- MIT license
Install
npm i file-typeyarn add file-typepnpm add file-typeOverview
Detect the file type of a file, stream, or data
Index
Variables
Functions
Classes
Type Aliases
Variables
variable supportedExtensions
const supportedExtensions: ReadonlySet<string>;Supported file extensions.
variable supportedMimeTypes
const supportedMimeTypes: ReadonlySet<string>;Supported MIME types.
Functions
function fileTypeFromBlob
fileTypeFromBlob: ( blob: Blob, options?: FileTypeOptions) => Promise<FileTypeResult | undefined>;Detect the file type of a [
Blob](https://nodejs.org/api/buffer.html#class-blob) or [File](https://developer.mozilla.org/en-US/docs/Web/API/File).Parameter blob
The [
Blob](https://nodejs.org/api/buffer.html#class-blob) used for file detection.Parameter options
Options to override default behavior.
Returns
The detected file type, or
undefinedwhen there is no match.Example 1
import {fileTypeFromBlob} from 'file-type';const blob = new Blob(['<?xml version="1.0" encoding="ISO-8859-1" ?>'], {type: 'text/plain',endings: 'native'});console.log(await fileTypeFromBlob(blob));//=> {ext: 'txt', mime: 'text/plain'}
function fileTypeFromBuffer
fileTypeFromBuffer: ( buffer: Uint8Array | ArrayBuffer, options?: FileTypeOptions) => Promise<FileTypeResult | undefined>;Detect the file type of a
Uint8ArrayorArrayBuffer.The file type is detected by checking the [magic number](https://en.wikipedia.org/wiki/Magic_number_(programming)#Magic_numbers_in_files) of the buffer.
In Node.js, it is recommended to use
fileTypeFromFile()instead when reading from a file path.Parameter buffer
A Uint8Array or ArrayBuffer representing file data. It works best if the buffer contains the entire file. It may work with a smaller portion as well.
Parameter options
Options to override default behavior.
Returns
The detected file type, or
undefinedwhen there is no match.
function fileTypeFromFile
fileTypeFromFile: ( filePath: string, options?: FileTypeOptions) => Promise<FileTypeResult | undefined>;Detect the file type of a file path.
The file type is detected by checking the [magic number](https://en.wikipedia.org/wiki/Magic_number_(programming)#Magic_numbers_in_files) of the file.
Only available in environments where
node:fsis available, such as Node.js. To read from a [File](https://developer.mozilla.org/docs/Web/API/File), seefileTypeFromBlob().Parameter filePath
The file path to examine.
Parameter options
Options to override default behavior.
Returns
The detected file type and MIME type or
undefinedwhen there is no match.
function fileTypeFromStream
fileTypeFromStream: ( stream: AnyWebReadableStream<Uint8Array>, options?: FileTypeOptions) => Promise<FileTypeResult | undefined>;Detect the file type of a [web
ReadableStream](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream).The file type is detected by checking the [magic number](https://en.wikipedia.org/wiki/Magic_number_(programming)#Magic_numbers_in_files) of the buffer.
If you have a Node.js
stream.Readable, convert it with [Readable.toWeb()](https://nodejs.org/api/stream.html#streamreadabletowebstreamreadable-options).Parameter stream
A [web
ReadableStream](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) streaming a file to examine.Parameter options
Options to override default behavior.
Returns
A
Promisefor an object with the detected file type, orundefinedwhen there is no match.
function fileTypeFromTokenizer
fileTypeFromTokenizer: ( tokenizer: ITokenizer, options?: FileTypeOptions) => Promise<FileTypeResult | undefined>;Detect the file type from an [
ITokenizer](https://github.com/Borewit/strtok3#tokenizer) source.This method is used internally, but can also be used for a special "tokenizer" reader.
A tokenizer propagates the internal read functions, allowing alternative transport mechanisms, to access files, to be implemented and used.
Parameter tokenizer
File source implementing the tokenizer interface.
Parameter options
Options to override default behavior.
Returns
The detected file type, or
undefinedwhen there is no match.An example is [
@tokenizer/http](https://github.com/Borewit/tokenizer-http), which requests data using [HTTP-range-requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests). A difference with a conventional stream and the [*tokenizer*](https://github.com/Borewit/strtok3#tokenizer), is that it can *ignore* (seek, fast-forward) in the stream. For example, you may only need and read the first 6 bytes, and the last 128 bytes, which may be an advantage in case reading the entire file would take longer.Example 1
import {makeTokenizer} from '@tokenizer/http';import {fileTypeFromTokenizer} from 'file-type';const audioTrackUrl = 'https://test-audio.netlify.com/Various%20Artists%20-%202009%20-%20netBloc%20Vol%2024_%20tiuqottigeloot%20%5BMP3-V2%5D/01%20-%20Diablo%20Swing%20Orchestra%20-%20Heroines.mp3';const httpTokenizer = await makeTokenizer(audioTrackUrl);const fileType = await fileTypeFromTokenizer(httpTokenizer);console.log(fileType);//=> {ext: 'mp3', mime: 'audio/mpeg'}
function fileTypeStream
fileTypeStream: ( webStream: AnyWebReadableStream<Uint8Array>, options?: StreamOptions & FileTypeOptions) => Promise<AnyWebReadableByteStreamWithFileType>;Returns a
Promisewhich resolves to the original readable stream argument, but with an addedfileTypeproperty, which is an object like the one returned fromfileTypeFromFile().This method can be handy to put in a stream pipeline, but it comes with a price. Internally
stream()builds up a buffer ofsampleSizebytes, used as a sample, to determine the file type. The sample size impacts the file detection resolution. A smaller sample size will result in lower probability of the best file type detection.
Classes
class FileTypeParser
class FileTypeParser {}constructor
constructor(options?: FileTypeOptions);property detectors
detectors: Detector[];File type detectors.
Initialized with a single entry holding the built-in detector function.
method fromBlob
fromBlob: (blob: Blob) => Promise<FileTypeResult | undefined>;Works the same way as fileTypeFromBlob, additionally taking into account custom detectors (if any were provided to the constructor).
method fromBuffer
fromBuffer: ( buffer: Uint8Array | ArrayBuffer) => Promise<FileTypeResult | undefined>;Works the same way as fileTypeFromBuffer, additionally taking into account custom detectors (if any were provided to the constructor).
method fromFile
fromFile: (filePath: string) => Promise<FileTypeResult | undefined>;Works the same way as fileTypeFromFile, additionally taking into account custom detectors (if any were provided to the constructor). Only available where
node:fsis available.
method fromStream
fromStream: ( stream: AnyWebReadableStream<Uint8Array>) => Promise<FileTypeResult | undefined>;Works the same way as fileTypeFromStream, additionally taking into account custom detectors (if any were provided to the constructor).
method fromTokenizer
fromTokenizer: (tokenizer: ITokenizer) => Promise<FileTypeResult | undefined>;Works the same way as fileTypeFromTokenizer, additionally taking into account custom detectors (if any were provided to the constructor).
method toDetectionStream
toDetectionStream: ( webStream: AnyWebReadableStream<Uint8Array>, options?: StreamOptions & FileTypeOptions) => Promise<AnyWebReadableByteStreamWithFileType>;Works the same way as fileTypeStream, additionally taking into account custom detectors (if any were provided to the constructor).
class TokenizerPositionError
class TokenizerPositionError extends Error {}constructor
constructor(message?: string);Type Aliases
type AnyWebReadableByteStreamWithFileType
type AnyWebReadableByteStreamWithFileType = AnyWebReadableStream<Uint8Array> & { readonly fileType?: FileTypeResult;};type AnyWebReadableStream
type AnyWebReadableStream<G> = WebReadableStream<G> | ReadableStream<G>;Either the Node.js ReadableStream or the
lib.dom.d.tsReadableStream. Related issue: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/60377
type Detector
type Detector = { id: string; detect: ( tokenizer: ITokenizer, fileType?: FileTypeResult ) => Promise<FileTypeResult | undefined>;};A custom file type detector.
Custom file type detectors are plugins designed to extend the default detection capabilities. They allow support for uncommon file types, non-binary formats, or customized detection behavior.
Detectors can be added via the constructor options or by directly modifying
FileTypeParser#detectors. Detectors provided through the constructor are executed before the default ones.### Example adding a detector
import {FileTypeParser} from 'file-type';import {detectXml} from '@file-type/xml';const parser = new FileTypeParser({customDetectors: [detectXml]});const fileType = await parser.fromFile('sample.kml');console.log(fileType);### Available third-party file-type detectors
- [@file-type/av](https://github.com/Borewit/file-type-av): Improves detection of audio and video file formats, with accurate differentiation between the two - [@file-type/cfbf](https://github.com/Borewit/file-type-cfbf): Detects Compound File Binary Format (CFBF) based formats, such as Office 97–2003 documents and
.msi. - [@file-type/pdf](https://github.com/Borewit/file-type-pdf): Detects PDF based file types, such as Adobe Illustrator - [@file-type/xml](https://github.com/Borewit/file-type-xml): Detects common XML file types, such as GLM, KML, MusicXML, RSS, SVG, and XHTML### Detector execution flow
If a detector returns
undefined, the following rules apply:1. **No Tokenizer Interaction**: If the detector does not modify the tokenizer's position, the next detector in the sequence is executed. 2. **Tokenizer Interaction**: If the detector modifies the tokenizer's position (
tokenizer.positionis advanced), no further detectors are executed. In this case, the file type remainsundefined, as subsequent detectors cannot evaluate the content. This is an exceptional scenario, as it prevents any other detectors from determining the file type.### Example writing a custom detector
Below is an example of a custom detector. This can be passed to the
FileTypeParservia thecustomDetectorsoption.import {FileTypeParser} from 'file-type';const unicornDetector = {id: 'unicorn',async detect(tokenizer) {const unicornHeader = [85, 78, 73, 67, 79, 82, 78]; // "UNICORN" in ASCII decimalconst buffer = new Uint8Array(unicornHeader.length);await tokenizer.peekBuffer(buffer, {length: unicornHeader.length, mayBeLess: true});if (unicornHeader.every((value, index) => value === buffer[index])) {return {ext: 'unicorn', mime: 'application/unicorn'};}return undefined;}};const buffer = new Uint8Array([85, 78, 73, 67, 79, 82, 78]);const parser = new FileTypeParser({customDetectors: [unicornDetector]});const fileType = await parser.fromBuffer(buffer);console.log(fileType); // {ext: 'unicorn', mime: 'application/unicorn'}Parameter tokenizer
The [tokenizer](https://github.com/Borewit/strtok3#tokenizer) used to read file content.
Parameter fileType
The file type detected by standard or previous custom detectors, or
undefinedif no match is found.Returns
The detected file type, or
undefinedif no match is found.
type FileTypeOptions
type FileTypeOptions = { customDetectors?: Iterable<Detector>;
/** An `AbortSignal` to cancel the detection. */ signal?: AbortSignal;
/** Specifies the byte tolerance for locating the first MPEG audio frame (e.g. `.mp1`, `.mp2`, `.mp3`, `.aac`).
Allows detection to handle slight sync offsets between the expected and actual frame start. Common in malformed or incorrectly muxed files, which, while technically invalid, do occur in the wild.
A tolerance of 10 bytes covers most cases.
@default 0 */ mpegOffsetTolerance?: number;};type FileTypeResult
type FileTypeResult = { /** One of the supported [file types](https://github.com/sindresorhus/file-type#supported-file-types). */ readonly ext: string;
/** The detected [MIME type](https://en.wikipedia.org/wiki/Internet_media_type). */ readonly mime: string;};type StreamOptions
type StreamOptions = { /** The default sample size in bytes.
@default 4100 */ readonly sampleSize?: number;};Package Files (1)
Dependencies (4)
Dev Dependencies (7)
Peer Dependencies (0)
No peer dependencies.
Badge
To add a badge like this oneto your package's README, use the codes available below.
You may also use Shields.io to create a custom badge linking to https://www.jsdocs.io/package/file-type.
- Markdown[](https://www.jsdocs.io/package/file-type)
- HTML<a href="https://www.jsdocs.io/package/file-type"><img src="https://img.shields.io/badge/jsDocs.io-reference-blue" alt="jsDocs.io"></a>
- Updated .
Package analyzed in 2545 ms. - Missing or incorrect documentation? Open an issue for this package.
