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

like-fs

v4.0.2

Published

Typed wrapper around the fs module and providing interfaces for cloud implementations

Downloads

820

Readme

like-fs

A thin abstraction layer for accessing local and cloud filesystems with an API like-fs

npm version Known Vulnerabilities

Table of Contents

Overview

like-fs is a thin layer of abstraction for accessing filesystems. This package includes two main classes. Those are LocalFilesystem and the TmpFilesystem. The most basic way to access the local filesystem is the LocalFilesystem. It is a simple wrapper around node's standard fs module, exposing the same API as the fs module. When possible, all functions are asynchronous returning a Promise so async/await can be used.

A key benefit of using this package is that directories don't have to be created, since every write operation, be it using streams or writing files directly, will ensure that the directory structure exists beforehand.

The TmpFilesystem is used to access files in the tmp directory. The difference between this and the LocalFilesystem is that the root is mounted to a directory in /tmp. All method calls to the TmpFilesystem are relative to this configured directory. So for example when calling fs.createReadStream('/images/logo.png') you're actually creating a ReadStream to /tmp/<some-dir>/images/logo.png

The package also includes an interface IOnlineFilesystem for implementations to access filesystems like AWS S3, Google Cloud Storage, Firebase Storage, etc.

like-fs is written in Typescript and is fully compatible with the dependency injection library Inversify and NestJS.

Example

import * as os from 'os';
import {TmpFilesystem, awaitWriteFinish} from "like-fs";

const fs = new TmpFilesystem({
	tmpDirectory: os.tmpdir() + '/my-project'
});

const readStream = fs.createReadStream('images/logo.png');
await fs.writeStreamToFile('images/logo-copy.png', readStream);

// awaitWriteFinish() is a helper function in utils.ts
await awaitWriteFinish(
	fs.createReadStream('images/logo.png')
		.pipe(fs.createWriteStream('images/logo-copy.png'))
);

Installation

The package is available via the npm registry

$ npm install like-fs
$ yarn add like-fs

Reference

LocalFilesystem

.createWriteStream(path: string, opts?: any): Writable;

Returns a WriteStream from the standard fs module. See fs.createWriteStream() for more details

.createReadStream(path: string, opts?: any): Readable;

Returns a ReadStream from the standard fs module. See fs.createReadStream() for more details

.readFile(path: string, encoding?: string): Promise<string|Buffer>;

Reads the file with the given encoding. If encoding is utf8 The return value will be a string, otherwise it'll be a Buffer

.exists(path: string): Promise;

Returns true if the file exists, otherwise will return false

.writeStreamToFile(path: string, stream: Readable, options?): Promise;

This is a helper function to asynchronously write a given ReadStream to a file. The Promise resolves once the write finishes.

.writeDataToFile(path: string, data: any, options?: any)

Works exactly like fs.writeFile()

.unlink(path: string): Promise;

Deletes the given file if it exists

.mkdir(path: string): Promise;

Creates a directory structure like mkdir -p. You only need this when you want to create a directory without writing a file. All methods which write files will automatically create the required directory structure beforehand.

.readDir(path: string): Promise<string[]>

Returns a string array of paths of the containing files and directories All paths are relative to the given path.

.lstat(path: string): Promise

Returns the size of a file

.dirSize(directory: string): Promise

Recursively calculates the sizes of all files and directories below the given path and returns the number in bytes

.touch(path: string): Promise

Creates an empty file at the given path

TmpFilesystem

Has the same methods as the LocalFilesystem with the only difference that all paths are relative to a directory in the /tmp directory. The path to this directory can be configured via the constructor

Cloud Filesystem

This package includes an interface IOnlineFilesystem which can be used to implement filesystems for different cloud storage providers.

Current implementations are

The interface IOnlineFilesystem exposes the same API as the local filesystems with two additional functions getDownloadUrl() and getUploadUrl().

This allows you to easily us the TmpFilesystem during development and testing and replace it with an actual implementation in your production environment