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

create-trigger

v0.2.0

Published

The Trigger.dev CLI to easily create and manage a Trigger.dev project

Downloads

9

Readme

✨ Create Trigger - Get started writing Trigger.dev code quickly

Trigger.dev is an open source platform that makes it easy to create event-driven background tasks directly your codebase.

You can run these tasks (or "workflows" as we like to cal them) in your existing Node.js repo, but if you don't have one of those (👋 Next.js devs) or you just want to try us out without the setup, this create-trigger CLI will scaffold out a project for you in just a few seconds, either starting from scratch or using one of our many templates.

💻 Usage

To scaffold out a new project using create-trigger, run any of the following three commands and answer the prompts:

npm

npm create trigger@latest

yarn

yarn create trigger

pnpm

pnpm create trigger@latest

You can also specify the template you want to use by passing an argument to the command, like so:

npm create trigger@latest github-stars-to-slack

Advanced Usage

| Option/Flag | Description | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | [template] | The name of the template to use, e.g. basic-starter | | -p, --projectName | The name of the project, as well as the name of the directory to create. Can be a path to a directory, e.g. ~/projects/my-project | | -k, --apiKey | The development API key to use for the project. Visit https://app.trigger.dev to get yours | | --noGit | Explicitly tell the CLI to not initialize a new git repo in the project | | --noInstall | Explicitly tell the CLI to not run the package manager's install command |

Folder structure

├── LICENSE
├── README.md
├── package.json
├── render.yaml
├── .env
├── .env.example
├── src
│   └── index.ts
└── tsconfig.json

src/index.ts

All your Trigger.dev workflow code will be in here, and this is the part you can start customizing.

.env

If provided, we'll save your development API Key here so running the project can connect to our servers.

render.yaml

A Render.com Blueprint file that makes it easy to deploy your repo as a Background Worker.

README.md

Contains useful instructions for getting started with the repo, including how to customize it, running it locally, testing it, and deploying it.

Next steps

After you successfully scaffold out your project, take a look at the README. If you have any issues, please feel free to email us at [email protected], or you can ask a question in our Discord server