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

@sayduck/asset-pipeline

v1.0.15

Published

Sayduck asset pipeline

Downloads

4

Readme

asset-pipeline

asset-pipeline CLI

oclif tests publish

Usage

$ npm install -g @sayduck/asset-pipeline
$ sayduck-pipeline COMMAND
running command...
$ sayduck-pipeline (--version)
@sayduck/asset-pipeline/1.0.7 darwin-arm64 node-v16.19.0
$ sayduck-pipeline --help [COMMAND]
USAGE
  $ sayduck-pipeline COMMAND
...

Commands

sayduck-pipeline gltf-to-glb

Convert a gltf to a glb

USAGE
  $ sayduck-pipeline gltf-to-glb -i <value> -o <value>

FLAGS
  -i, --input=<value>   (required)
  -o, --output=<value>  (required)

DESCRIPTION
  Convert a gltf to a glb

See code: dist/commands/gltf-to-glb.ts

sayduck-pipeline help [COMMANDS]

Display help for sayduck-pipeline.

USAGE
  $ sayduck-pipeline help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for sayduck-pipeline.

See code: @oclif/plugin-help

sayduck-pipeline plugins

List installed plugins.

USAGE
  $ sayduck-pipeline plugins [--core]

FLAGS
  --core  Show core plugins.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ sayduck-pipeline plugins

See code: @oclif/plugin-plugins

sayduck-pipeline plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ sayduck-pipeline plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ sayduck-pipeline plugins add

EXAMPLES
  $ sayduck-pipeline plugins:install myplugin

  $ sayduck-pipeline plugins:install https://github.com/someuser/someplugin

  $ sayduck-pipeline plugins:install someuser/someplugin

sayduck-pipeline plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ sayduck-pipeline plugins:inspect PLUGIN...

ARGUMENTS
  PLUGIN  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ sayduck-pipeline plugins:inspect myplugin

sayduck-pipeline plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ sayduck-pipeline plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Installs a plugin into the CLI.
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
  the CLI without the need to patch and update the whole CLI.


ALIASES
  $ sayduck-pipeline plugins add

EXAMPLES
  $ sayduck-pipeline plugins:install myplugin

  $ sayduck-pipeline plugins:install https://github.com/someuser/someplugin

  $ sayduck-pipeline plugins:install someuser/someplugin

sayduck-pipeline plugins:link PLUGIN

Links a plugin into the CLI for development.

USAGE
  $ sayduck-pipeline plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Links a plugin into the CLI for development.
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ sayduck-pipeline plugins:link myplugin

sayduck-pipeline plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ sayduck-pipeline plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sayduck-pipeline plugins unlink
  $ sayduck-pipeline plugins remove

sayduck-pipeline plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ sayduck-pipeline plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sayduck-pipeline plugins unlink
  $ sayduck-pipeline plugins remove

sayduck-pipeline plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ sayduck-pipeline plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ sayduck-pipeline plugins unlink
  $ sayduck-pipeline plugins remove

sayduck-pipeline plugins update

Update installed plugins.

USAGE
  $ sayduck-pipeline plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

sayduck-pipeline scene-to-gltf

Generates a gltf given a scene.json

USAGE
  $ sayduck-pipeline scene-to-gltf -i <value> -o <value>

FLAGS
  -i, --input=<value>   (required)
  -o, --output=<value>  (required)

DESCRIPTION
  Generates a gltf given a scene.json

See code: dist/commands/scene-to-gltf.ts