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

serverless-offline-watcher

v1.1.0

Published

Run arbitrary commands when files are changed while running serverless-offline

Downloads

14,141

Readme

serverless-offline-watcher

Run arbitrary commands when files are changed while running serverless-offline

Install

npm install --save-dev serverless-offline-watcher

Usage

Serverless configuration

Add it to your list of plugins, and custom config for what you want to do on files being changed.

The path property may be a string, or array of strings. They be file paths, directory paths or glob patterns. Under the hood this library uses chokidar for file watching and picomatch for glob patterns, so you can see there documentation for more details about supported patterns.

The event type and the changed file path are available in environment variables WATCHER_EVENT_TYPE and WATCHER_EVENT_PATH respectively. The event type comes from chokidar and is one of "add" | "addDir" | "change" | "unlink" | "unlinkDir".

serverless.yaml:

plugins:
  - serverless-offline
  - serverless-offline-watcher

custom:
  serverless-offline-watcher:
    - path: src/index.ts
      command: echo "index.ts was modified!"
    - path:
        - src/api
        - src/cow/*.js
      command:
        - echo "api folder or js file in cow folder was modified!"
        - echo "the command-option can also be an array of commands"
    - path:
        - src/**/**
      # this prints for example "received change event for src/path/to/file.ts"
      command: "echo received $WATCHER_EVENT_TYPE event for $WATCHER_EVENT_PATH"

serverless.js / serverless.ts:

export default {
  plugins: [
    "serverless-offline",
    "serverless-offline-watcher",
  ],
  custom: {
    'serverless-offline-watcher': [
      {
        path: "src/index.ts",
        command: `echo "index.ts was modified!"`,
      },
      {
        path: ["src/api", "src/cow/*.js"],
        command: `echo "api folder or js file in cow folder was modified!"`,
      },
    ],
  },
}

In addition to running arbitrary shell commands, the plugin can also invoke a hook in some other serverless plugin, with the hook option. The following will ask serverless-offline to clear its Worker cache when a file in the src directory is changed:

    - path:
        - src/**/*
      hook:
        - offline:functionsUpdated

Running serverless-offline

Use serverless offline start instead of serverless offline, if you aren't already. This is necessary for serverless-offline to fire off init and end lifecycle hooks so that we can start and stop the watch server correctly.