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

my613-cli

v0.1.0

Published

CLI interface for My613

Downloads

2

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

plan8plan8

Keywords

My613

Readme

my613-cli

CLI interface for My613

npm install -g my613-cli
my613 login
my613 schema-fetch

Usage

my613 login [url] [token]

Login to My613 using given My613 URL and token. Prompts for url and token if they are not provided. Credentials are stored in .netrc file in user's HOME folder.

my613 logout

Clear stored credentials.

my613 graphiql

Opens GraphiQL console for your app in your browser.

my613 schema-fetch [SCHEMA_FILE] [--force]

Fetch My613 JSON schema to SCHEMA_FILE file (My613Schema.json if not provided).

If --force flag is not set, it will not run if schema file already exists.

my613 schema-push [SCHEMA_FILE] [--dry-run --force]

Push JSON schema from SCHEMA_FILE (defaults to My613Schema.json) to My613 API to perform a migration. Validates the schema and runs the migration, if it only includes safe operations.

If the migration includes destructive operations, --force flag must be used to run it.

If --dry-run flag is given, the command only validates the schema and displays the migration without running.

my613 schema-relay OUTPUT

Get Relay compatible GraphQL schema from My613 API at HOST. OUTPUT is a file name. If output is specified, result is written into it. Otherwise result is written to stdout.

Options

-u MY613_URL --url MY613_URL

Your My613 application host (eg https://YOURAPP.my613.com). Can be set either with this flag or via MY613_URL environment variable. If you use my613 login, this parameter overrides stored credentials.

-t MY613_TOKEN --token MY613_TOKEN

Your My613 application authorization token. Can be set either with this flag or via MY613_TOKEN environment variable. If you use my613 login, this parameter overrides stored credentials.