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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@scayle/storefront-cli

v0.17.3

Published

SCAYLE Storefront command line utility

Vulnerabilities

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

Links

Git

Maintainers

hector_gonzalez_ayhector_gonzalez_ayay-henribeckay-henribecklouisa_schmidt_aylouisa_schmidt_ayconnor-pearson-ayconnor-pearson-aymarcel-domke-aymarcel-domke-aykyosifovkyosifovscayle-automationscayle-automationcloud-panel-aycloud-panel-ay

Keywords

oclif

Readme

@scayle/storefront-cli

Storefront CLI

The SCAYLE Storefront command-line interface (CLI) tool accelerates feature adoption in SCAYLE Storefront tenant projects by simplifying the integration of new features and updates from the Storefront Application. It allows tenants to selectively add individual feature components, even if their project is based on an older Storefront Application version, avoiding the need for a full Storefront Application upgrade.

The CLI handles the complexities of component delivery and integration, allowing developers to focus on customizing and implementing the feature's functionality. It automatically fetches the necessary components based on the selected feature and Storefront Application version, manages potential file conflicts, and optionally includes unit tests.
This streamlined workflow significantly reduces manual effort and accelerates the overall development process.

Usage

Recommended Usage

To always use the current version of the CLI we recommend to use the package as remote package pnpx or npx. This will always fetch the current version of the Storefront CLI.

# Using PNPM
pnpx @scayle/storefront-cli COMMAND

# Using NPX
npx @scayle/storefront-cli COMMAND

Installed Usage

$ npm install -g @scayle/storefront-cli
$ sfcli COMMAND
running command...
$ sfcli (--version)
@scayle/storefront-cli/0.17.3 linux-x64 node-v24.13.0
$ sfcli --help [COMMAND]
USAGE
  $ sfcli COMMAND
...

Commands

sfcli commands

List all sfcli commands.

USAGE
  $ sfcli commands [--json] [-c id|plugin|summary|type... | --tree] [--deprecated] [-x | ] [--hidden]
    [--no-truncate | ] [--sort id|plugin|summary|type | ]

FLAGS
  -c, --columns=<option>...  Only show provided columns (comma-separated).
                             <options: id|plugin|summary|type>
  -x, --extended             Show extra columns.
      --deprecated           Show deprecated commands.
      --hidden               Show hidden commands.
      --no-truncate          Do not truncate output.
      --sort=<option>        [default: id] Property to sort by.
                             <options: id|plugin|summary|type>
      --tree                 Show tree of commands.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List all sfcli commands.

See code: @oclif/plugin-commands

sfcli deploy

The deploy command will initiate a new deployment to SCAYLE PaaS and and display the build logs.

USAGE
  $ sfcli deploy -t <value> -s <value> -e <value> --deploy-token <value> [--json] [--log-level
    debug|warn|error|info|trace] [-h] [--no-config-file] [-g <value>]

FLAGS
  -e, --env-key=<value>       (required) [env: SCAYLE_CLI_ENV_KEY] Env Key is needed for identifying the correct
                              environment.
  -g, --git-ref=<value>       [env: SCAYLE_CLI_GIT_REF] Git ref is used to checkout the specific version of the app that
                              should be deployed
  -h, --no-header             Disable initial header print for the CLI.
  -s, --shop-key=<value>      (required) [env: SCAYLE_CLI_SHOP_KEY] Shop Key is needed for identifying the correct shop.
  -t, --tenant-space=<value>  (required) [env: SCAYLE_CLI_TENANT_SPACE] Tenant Space is needed for identifying the
                              correct context within the SCAYLE Core System.
      --deploy-token=<value>  (required) [env: SCAYLE_CLI_DEPLOY_TOKEN] Deploy Token is needed to authenticate against
                              the SCAYLE PaaS System.
      --no-config-file        [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  The deploy command will initiate a new deployment to SCAYLE PaaS and and display the build logs.

EXAMPLES
  $ sfcli deploy

See code: src/commands/deploy.ts

sfcli features add [PACKAGES]

Adds a SCAYLE Storefront feature module to Storefront projects,

USAGE
  $ sfcli features add [PACKAGES] -a <value> [--json] [--log-level debug|warn|error|info|trace] [-h]
    [--no-config-file] [-c] [-f]

ARGUMENTS
  [PACKAGES]  Directly install one or more specific packages, bypassing the multi-select prompt.

FLAGS
  -a, --access-token=<value>  (required) Access Token for Storefront Application repository
  -c, --should-copy           Copy relevant feature module components and related files
  -f, --should-override       Override existing files while copying relevant feature module components and related files
  -h, --no-header             Disable initial header print for the CLI.
      --no-config-file        [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  Adds a SCAYLE Storefront feature module to Storefront projects,
  with an option to include the associated Vue components and unit tests.

EXAMPLES
  $ sfcli features add

See code: src/commands/features/add.ts

sfcli features list

Lists the available feature packages which can be installed with the add command

USAGE
  $ sfcli features list -a <value> [--json] [--log-level debug|warn|error|info|trace] [-h] [--no-config-file]

FLAGS
  -a, --access-token=<value>  (required) Access Token for Storefront Application repository
  -h, --no-header             Disable initial header print for the CLI.
      --no-config-file        [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  Lists the available feature packages which can be installed with the add command

EXAMPLES
  $ sfcli features list

See code: src/commands/features/list.ts

sfcli help [COMMAND]

Display help for sfcli.

USAGE
  $ sfcli help [COMMAND...] [-n]

ARGUMENTS
  [COMMAND...]  Command to show help for.

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

DESCRIPTION
  Display help for sfcli.

See code: @oclif/plugin-help

sfcli setup

The setup command will guide the user through a series of interactive prompts to gather the necessary information for configuring the Storefront Application.

USAGE
  $ sfcli setup -t <value> -a <value> [--json] [--log-level debug|warn|error|info|trace] [-h]
    [--no-config-file] [-p <value>] [-o] [-e]

FLAGS
  -a, --admin-api-token=<value>  (required) Admin API token will be used for authentication and authorization when
                                 accessing data from the SCAYLE Core System.
  -e, --only-env                 Setup only local environment variable as part of a .env file and skips creation of shop
                                 config, as well as translation files.
  -h, --no-header                Disable initial header print for the CLI.
  -o, --should-override          Override existing files while copying relevant feature module components and related
                                 files
  -p, --parent-shop-key=<value>  Shop key to setup a shop directly.
  -t, --tenant-space=<value>     (required) Tenant Space is needed for identifying the correct context within the SCAYLE
                                 Core System.
      --no-config-file           [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  The setup command will guide the user through a series of interactive prompts to gather the necessary information for
  configuring the Storefront Application.

EXAMPLES
  $ sfcli setup

See code: src/commands/setup/index.ts

sfcli setup cms contentful

Configures the Storefront Application to use Contentful as the CMS provider.

USAGE
  $ sfcli setup cms contentful -i true|false -s <value> --access-token <value> --preview-token <value> --management-token
    <value> [--json] [--log-level debug|warn|error|info|trace] [-h] [--no-config-file]

FLAGS
  -h, --no-header                      Disable initial header print for the CLI.
  -i, --import-content-model=<option>  (required) Import the content model in to the CMS. This command is only intended
                                       to be used with empty CMS spaces.
                                       <options: true|false>
  -s, --space-id=<value>               (required) The Contentful Space ID you want to use.
      --access-token=<value>           (required) Delivery API access token for Contentful. Used by the app to fetch
                                       published content.
      --management-token=<value>       (required) Content Management API access token for Contentful. Required for
                                       importing the content model.
      --no-config-file                 [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.
      --preview-token=<value>          (required) Preview API access token for Contentful. Allows the app to fetch
                                       draft/unpublished content for preview purposes.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  Configures the Storefront Application to use Contentful as the CMS provider.

EXAMPLES
  $ sfcli setup cms contentful

See code: src/commands/setup/cms/contentful.ts

sfcli setup cms contentstack

Configures the Storefront Application to use Contentstack as the CMS provider.

USAGE
  $ sfcli setup cms contentstack -i true|false -k <value> -d <value> -p <value> -r na|eu|au|azure-na|azure-eu|gcp-na|gcp-eu
    -e <value> -m <value> [--json] [--log-level debug|warn|error|info|trace] [-h] [--no-config-file] [-b <value>]

FLAGS
  -b, --branch=<value>                 [default: main] Branch UID used with Contentstack’s branch feature
  -d, --delivery-token=<value>         (required) Content Delivery Token used for fetching published content via Content
                                       Delivery API.
  -e, --environment=<value>            (required) Environment name in Contentstack determines which environment to use
                                       for content retrieval.
  -h, --no-header                      Disable initial header print for the CLI.
  -i, --import-content-model=<option>  (required) Import the content model in to the CMS. This command is only intended
                                       to be used with empty CMS spaces.
                                       <options: true|false>
  -k, --api-key=<value>                (required) Contentstack Stack API Key required to identify the target stack.
  -m, --management-token=<value>       (required) Contentstack Management Token required for importing the content model
                                       via the Management API.
  -p, --preview-token=<value>          (required) Content Preview Token used for fetching draft/preview content via
                                       Content Preview API.
  -r, --region=<option>                (required) Region for the stack
                                       <options: na|eu|au|azure-na|azure-eu|gcp-na|gcp-eu>
      --no-config-file                 [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  Configures the Storefront Application to use Contentstack as the CMS provider.

EXAMPLES
  $ sfcli setup cms contentstack

See code: src/commands/setup/cms/contentstack.ts

sfcli setup cms storyblok

Configures the Storefront Application to use Storyblok as the CMS provider.

USAGE
  $ sfcli setup cms storyblok -i true|false -s <value> --access-token <value> [--json] [--log-level
    debug|warn|error|info|trace] [-h] [--no-config-file] [-p <value>]

FLAGS
  -h, --no-header                      Disable initial header print for the CLI.
  -i, --import-content-model=<option>  (required) Import the content model in to the CMS. This command is only intended
                                       to be used with empty CMS spaces.
                                       <options: true|false>
  -p, --personal-access-token=<value>  The Storyblok Personal Access Token for the Management API. Required for
                                       importing the content model.
  -s, --space-id=<value>               (required) The unique Space ID for your Storyblok space. This identifies the
                                       specific Storyblok space to connect to.
      --access-token=<value>           (required) The Storyblok Preview or Public Access Token used for the Content
                                       Delivery API.
      --no-config-file                 [env: SCAYLE_CLI_NO_CONFIG_FILE] Disable generating a config file.

GLOBAL FLAGS
  --json                Format output as json.
  --log-level=<option>  [default: info] Specify level for logging.
                        <options: debug|warn|error|info|trace>

DESCRIPTION
  Configures the Storefront Application to use Storyblok as the CMS provider.

EXAMPLES
  $ sfcli setup cms storyblok

See code: src/commands/setup/cms/storyblok.ts

License

Licensed under the MIT License

What is SCAYLE?

SCAYLE is a full-featured e-commerce software solution that comes with flexible APIs. Within SCAYLE, you can manage all aspects of your shop, such as products, stocks, customers, and transactions.

Learn more about SCAYLE’s architecture and commerce modules in the Docs.

Other channels