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

@sprinklrjs/create-sprinklr-app

v2.1.2

Published

A CLI tool to bootstrap a Sprinklr App that can be installed as an external app in Sprinklr Platform

Downloads

295

Readme

Create Sprinklr App

Create Sprinklr App provides a way to quickly get started on integrating custom components inside Sprinklr. To get started we simply need to run

$ npx @sprinklrjs/create-sprinklr-app

This will prompt you for some information needed to bootstrap the application. Once you are done this will create a folder with an application. If you open this folder, you will see a manifest.json file at the root of your application which will look something like this -

{
  "name": "my-custom-app",
  "version": "0.1.0",
  "basePath": "http://localhost:3000",
  "integrationType": "VIRTUALIZED",
  "widgets": [
    {
      "id": "todo",
      "title": "Todo List",
      "url": "/todo",
      "scopes": ["RECORD_PAGE"]
    }
  ]
}

Manifest.json

name

Name of your custom application

version

Current version of the application. Sprinklr follows semantic versioning

basePath

Optional parameter indicating the base URL from where the application is being served. This is useful while developing your application to quickly test your compoents.

widgets

Array of the custom components to be added. Each component config object looks something like this

{
  "id": "todo",
  "title": "Todo List",
  "url": "/todo",
  "scopes": ["RECORD_PAGE"],
  "props": {
    "height": "500px"
  }
}

id Id of the custom component.

title Name of the component.

url Relative url of the component. This is appended to the basePath of where the application is hosted, to render the custom component.

scopes In what areas of application to surface this component. Currently only RECORD_PAGE is supported.

props Properties to be passed to the component. For eg to set a fixed height for your component pass the height props as follows

"props": {
  "height": "500px"
}