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

@battis/partly-gcloudy

v0.6.0

Published

Idiosyncratic collection of interactions with `gcloud` CLI tool

Downloads

86

Readme

@battis/partly-gcloudy

Idiosyncratic collection of interactions with gcloud CLI tool

npm version Module type: ESM

Install

npm i @battis/partly-gcloudy

Usage

This is an ESM module that depends on other ESM modules, and so really can only feasibly be imported by ESM modules.

import * as gcloud from '@battis/partly-gcloudy';

await gcloud.init();
await gcloud.app.deploy();

Design

This is really designed to meet my needs (type-safe, fat-finger-preventative, repetitive interactions with Google Cloud). There are a few basic principles:

  • Property names match up with the gcloud CLI verbs. gcloud projects describe becomes gcloud.projects.describe()
  • Method parameters are the names used in the corresponding gcloud CLI tool documentation, camelCased. gcloud projects describe PROJECT_ID_OR_NUMBER becomes gcloud.projects.describe({ projectId: 'flim-flam-1234' })
  • Methods are typed to hint their parameters, which are passed as object arguments to facilitate hyper-aggressive type-checking in a loosey-goosey manner. Argument order is too much to worry about. gcloud.projects.describe({ projectId: 'flim-flam-1234' })
  • Methods are information-agnostic -- if you don't pass some or all of the arguments, they'll interactively ask the user for what they need. gcloud.projects.create() works. If it really can't be done, it will fail with a demonstrative error.
  • All "verb" methods are asynchronous.
  • All input is validated to the extent possible.

gcloud.*.input*() and gcloud.*.select*()

Where user input may be required (or validated) the different types of input relevant to a gcloud verb are grouped within the property.

let projectId = '_$argle-bargle';
projectId = await gcloud.projects.inputProjectId({ projectId });

The initial projectId value is invalid, will fail the validation, and result in interactive user-input to choose a valid project ID.

Batch operations

As I need them, I am packaging up modular batches of operations in the gcloud.batch namespace.

import gcloud from '@battis/partly-gcloudy';

await gcloud.batch.appEnginePublish();

This will create a Google Cloud project (or reuse an existing one, if you enter an existing project ID or have your environment variable PROJECT set), configure an App Engine Instance in that project, if necessary, and deploy the current project to that App Engine instance.