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

@brokenrubik/ss-build-tools

v2.0.5

Published

## Usage on existing projects:

Downloads

35

Readme

SuiteScript Build Tools

Usage on existing projects:

  1. Install dependency in your project (started from ss-template)
npm i -D @brokenrubik/ss-build-tools@latest

Example package.json:

{
  "scripts": {
    "deploy": "ss-deploy",
    "build": "ss-build",
    "watch": "ss-watch"
  }
}

Building

The default TypeScript source path is set to "src/TypeScript". If you want to specify a different path you can either:

  • Use the TS_SOURCE_PATH environment variable
  • Use the --source-path command line argument

For example:

{
  "scripts": {
    "build": "ss-build --source-path src/ts-files"
  }
}

The output of the build command will be be placed in the outDir specified in your tsconfig.json file.

We recomend setting the outDir to "src/FileCabinet/SuiteScripts/<Project Name>".

ss-build -js flag

You can pass the -js flag to the build command to copy files from the src/SuiteScripts directory to the src/FileCAbinet/SuiteScripts directory.

Deploying

Running the deploy command will automatically build, and pass the arguments. You can specify the source path in the same way as the build command.

The files in "src/FileCabinet/SuiteScripts" will be deployed using suitecloud commands.

Watch Mode (Experimental)

Running the watch command will automatically build and deploy on file changes.

This is useful for development, but it is not recommended to use this in production.

The watch mode will incrementally build the TypeScript output, and deploy files that have changed.

You can specify the source path in the same way as the build command. The default is "src/TypeScript".

{
  "scripts": {
    "watch": "ss-watch --source-path src/TypeScript"
  }
}

Prefixing the project's File Cabinet directory

You can use the FILE_PATH environment variable to prefix the project's dir.

For example, if you create a .env file with:

FILE_PATH=my-custom-scripts

Then, only files under src/FileCabinet/SuiteScripts/my-custom-scripts will be deployed.