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

@travelhubx/aws

v0.0.12

Published

This library was generated with [Nx](https://nx.dev).

Downloads

190

Readme

aws

This library was generated with Nx.

Running unit tests

Run nx test aws to execute the unit tests via Jest.

Publishing the package to NPM

A. Run 'nx build aws' to prepare the library for publishing.

B. In libs/aws package.json file change the library version to a newer one (ex: from 0.0.4 to 0.0.5)

C. Change directory to libs/aws and run the following scripts:

  1. Run npm run build
  2. Run npm run bundle

D. Change directory to dist/libs/aws and do the following:

  1. In the generated package.json change name from "@thx/aws" to "@travelhubx/aws".
  2. Run npm login to authenticate with your npm account and follow the instructions.
  3. Run npm publish --access=public

Issues:

  1. code ENEEDAUTH. You probably forgot to register. Go back to previous step and retry
  2. 402 Payment Required . You either need a paid account or you need to publish your library publicly. Don’t forget --access=public in your command line or add a PublishConfig inside your package.json.
  3. 403 Forbidden . When publishing, you need to increase your version number.
  4. 404 Not Found — Scope not found . In our case, we defined a scope as @thx instead of our organization name @travelhubx. You need to follow step 1 from section D.