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

@giovannicuriel/aws-alternative

v1.0.5

Published

AWS lib wrapper

Downloads

3

Readme

aws-alternative

AWS library wrapper that easily switches from localstack and actual AWS services.

Why

If you develop software using AWS services or to be executed within a container in EC2, ECS, or whatever, it is very likely that you first tried to test it locally with LocalStack. Therefore, there are a few changes that you must do in order to redirect all AWS SDK calls to your localstack instance instead of AWS ones:

  AWS.config.update({
    region: 'us-east-1',
    credentials: {
      accessKeyId: 'dummy-access-key',
      secretAccessKey: 'dummy-secret-key'
    },
    endpoint: 'http://192.168.240.1:4569'
  })

Everytime. For all services. Different ports for each service.

This is where this library might help. By using it, you could just enable localstack by setting one environment variable and every service object is properly configured. If you unset that environment variable, it will not perform any configuration and the services your software will use are from AWS with no code changes.

How

If you'd like to use localstack, you should set LOCALSTACK_ENABLED environment variable. This library doesn't care about which value it is, as long as it is defined. For instance:

export LOCALSTACK_ENABLED=1

is enough to use localstack.

In your software, you must select which service object you need:

// Create a SQS service object.
const sqs = require('aws-alternative')('sqs')

// Create a new DynamoDB object. This will be used to create a DocumentClient
// object
const dynamo = require('aws-alternative')('dynamodb')
const db = new AWS.DynamoDB.DocumentClient({service: dynamo})

Known problems

I did not use every service available at AWS. There might be a few ones which name is not correct. Feel free to fix them (doing so is not hard at all) and I'd be more than happy to review your PR. Spread the love!.