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

@sitecore-search/cli

v2.6.3

Published

Sitecore Search SDK cli

Downloads

7,787

Readme

@sitecore-search/cli

Command line tool for the Sitecore Discover React SDK.

Installation

npm install --save-dev @sitecore-search/cli

Running CLI

To run the cli execute the following command on a terminal:

npx sc-search

followed by any of the available options or actions.

E.g.: npx sc-search --version

Global options

| Option | Description | |-------------|----------------------| | --version | Shows version number | | -h, --h | Shows help |

Available actions

| Command | Description | Aliases | Options | |--------------------------|-------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | new-widget | Generates files to create a new widget | nw | --verbose (-v): Run with verbose logging --overwrite (-w): Overwrite the destination --suffix (-s): Template file suffix --template (-t): The template id --name (-n): The template component name --default-name (-d): Use the default template component name --output (-o): The path where you want your template --language (-l): The template language --styling (-st): The template styling |

E.g.: npx sc-search new-widget -v -n MyWidget -o widget/path -w

will create a new Widget named MyWidget in the widget/path and if the Widget already exist will overwrite it. If any of the parameters are omitted, the cli will prompt some questions to complete the missing information.

Settings

The cli will try to read a file named .sc-search-settings.json to get some settings. That file should be present in the same folder as the command has been called. Here is an example about that file should look like:

{
    "components-path": "src-test/components"
}

The destination of the generated widgets can be set there.