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

ryuu

v4.4.7

Published

Domo App Dev Studio CLI, The main tool used to create, edit, and publish app designs to Domo

Downloads

965

Readme

Ryuu CLI

A command line interface to the Domo App Framework.

npm version install size npm downloads Known Vulnerabilities

Documentation

Contributing

Recommended Workflow:

  1. Create new branch (named "DOMO-XXXXXX")
  2. Make Changes
  3. Commit Changes
  4. Test changes (if necessary, release an alpha/beta/tagged version)
  5. Make pull request
  6. After pull request is merged to master, release a full version via npm run release, then release it to brew and chocolatey

Building

To build the CLI, run

npm run build

All necessary files will be built/copied into the dist folder.

Linking

In order for easier development with ryuu-proxy or ryuu-client, use linking.

  1. cd into the folder that you cloned ryuu-proxy/ryuu-client to, ex. cd ~/ryuu/ryuu-proxy
  2. npm link
  3. cd into the folder that you cloned domoapps-cli to, ex cd ~/ryuu/domoapps-cli
  4. npm link @domoinc/ryuu-proxy (this is because the package name for ryuu-proxy is @domoinc/ryuu-proxy) Use npm unlink in both locations to unlink the repositories later if needed.

Debugging

Debugging is most easily done via the the native node extension in VSCode.

  1. Run node and point it to the built domo.js file in dist/bin after building
    node --inspect-brk ~/ryuu/domoapps-cli/dist/bin/domo.js [command]
  2. ⌘ Command + ⇧ Shift + P to open the VSCode command palette.
  3. Select Debug: Attach to Node Process and select the node process you just started in step 1.
  4. The process should move your active window to the beginning of the CLI (generally domo.ts), and you can start debugging.

TIPS:

  • Set breakpoints in the .ts files for domoapps-cli, and in the .js files for all node modules, unless you've utilized npm link like for ryuu-client/ryuu-proxy, in which case you can use the .ts files as well.
  • If your breakpoint isn't being hit, try to "advance" the code to make sure the breakpoint is being set in the right file.

Versioning

This project utilizes standard-version. Versions should be bumped via the npm run release commands.

Releasing

Versions should be released on NPM until confirmed stable, at which point brew and chocolatey can be released

  • npm run release
  • npm run releaseAlpha
  • npm run releaseBeta
  • npm run releaseBrew
  • npm run releaseChocolatey

Committing the latest Phoenix version

npm install @domoinc/domo-phoenix@latest
npm run build:phoenix
git add templates/**/domoPhoenix*.js
git commit -m "Update to the latest Phoenix version"