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

aws-s3-utils

v1.1.0

Published

Node.js library providing high-level wrapper for convenient AWS S3 capabilities

Downloads

2

Readme

aws-s3-utils

What is this?

Node.js library providing high-level promise-based wrapper for convenient AWS S3 capabilities such as downloading an S3 object as a string or directly to a file.

Installation

yarn add aws-s3-utils

Usage

Download to String

Downloading an S3 object to a string is implementing streams behind the scenes, and works as simple as defining a Map for the options and invoking the downloadToString promise:

const awsS3Util = require('aws-s3-utils')

const params = new Map()
params.set('config', { credentials: { accessKeyId: 'id', secretAccessKey: 'key' } })
params.set('object', { Bucket: 'somebucket', Key: 'filename' })

awsS3Util.downloadToString(params)
  .then((s3Contents) => {
  	console.log(`downloaded s3 object content is: ${s3Contents}`)
  })

You can also pass a key that sets a character byte limit on the length of the string:

params.set('maxSize', 2)

Download to File

Downloading an S3 object to a file is also implemented using streams and works by invoking the downloadToFile promise.

The downloadToFile supports the following download settings on the provided Map options:

  • If tempDirectory is specified then the library will create a unique temporary directory inside the tempDirectory directory and download the file there.
  • If destFile is specified then the downloaded file wil be named using this filename.
  • If destDirectory is specified then the downloaded file will be placed directly inside this directory without creating any upper level unique directory. If both this option and tempDirectory are specified then this option takes precedence.
const awsS3Util = require('aws-s3-utils')

const params = new Map()
params.set('config', { credentials: { accessKeyId: 'id', secretAccessKey: 'key' } })
params.set('object', { Bucket: 'somebucket', Key: 'filename' })
params.set('download', { tempDirectory: '/tmp' })

awsS3Util.downloadToFile(params)
  .then((filepath) => {
  	console.log(`downloaded s3 object content is: ${s3Contents}`)
  })

Tests

Project tests:

yarn test

Project linting:

yarn lint
yarn lint:fix

View Coverage

yarn coverage:view

Developer Commit

The project uses the commitizen tool for standardizing changelog style commit messages so you should follow it as so:

git add .           # add files to staging
yarn commit      # use the wizard for the commit message