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

fs-backblaze

v1.0.1

Published

A drop-in replacement for fs. Can be used to perform the same file actions as fs offers, but using Backblaze instead of the local filesystem.

Downloads

3

Readme

fs-backblaze

A drop-in replacement for the fs module, for Backblaze. Used to treat a Backblaze bucket as a filesystem, without having to rewrite your code to switch from fs to fs-backblaze

API Key

Generate an API key for your use case. Generating keys can be done here: https://secure.backblaze.com/app_keys.htm It's advised to create an Application Key and not use the master key. Always generate a bucket-specific application key, a key with "all" access has not been tested.

Setup

Setting up the Backblaze filesystem only requires 1 step after which it can be used:

const FSBackblaze = require('fs-backblaze'); const fs = new FSBackblaze(bucketName, applicationKeyId, applicationKey);

Using this module

Simply use all methods the same way as you would with the regular fs module

Supported methods:

| Method | Supported? | |----------|:-------------:| | access | no | | appendFile | no | | chmod | no | | chown | no | | close | YES | | createReadStream | YES | | createWriteStream | no | | lchmod | no | | lchown | no | | link | no | | lstat | no | | mkdir | no | | mkdtemp | no | | open | YES | | read | YES | | readdir | YES | | readFile | YES | | readlink | no | | realpath | no | | rename | no | | rmdir | no | | stat | YES | | symlink | no | | truncate | no | | unlink | no | | unwatchFile | no | | utimes | no | | watch | no | | watchFile | no | | write | no | | writeFile | no |

It could be that some methods with optional arguments aren't implemented the way you expect it to. If you encounter such method, please file an issue on the Bitbucket and it will be implemented asap. PR's are very welcome too.