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

relay-watcher

v0.0.7

Published

Run the relay compiler on save

Downloads

3

Readme

VSCode Relay Watcher

Visual Studio Marketplace Version Visual Studio Marketplace Installs

Run the relay compiler on save.

By default relay --watch

  • requires watchman to be installed
  • runs as a separate command

Watchman is cumbersome to install and frequently throws errors within docker containers.

Install

Install options:

  • Download from the marketplace
  • Install from the command line: code --install-extension pinterest.relay-watcher
  • Search for Relay Watcher in the VS Code extensions panel

Features

  • Run the relay compiler on save
  • Requires no configuration
  • Supports multiple package managers: npm and yarn
  • Supports VSCode Remote
  • Uses VSCode's internal file watcher instead of watchman.

Requirements

  • relay.config.js file(s) in the workspace root or subdirectories.
  • relay-compiler package should be installed next to each Relay configuration file

Extension Settings

| Setting | Type (default) | Description | | -------------------------------- | --------------------------------------------- | --------------------------------------------------- | | relayWatcher.enableTelemetry | boolean (true) | Enable/disable telemetry | | relayWatcher.logLevel | enum: 'info', 'debug', 'off' ('info') | Output log level | | relayWatcher.showOutputOnError | boolean (true) | Show output log when relay compiler throws an error |

Extension Commands

| Setting | Description | | -------------------------------- | ----------------------- | | relayWatcher.enable | Enable the extension | | relayWatcher.disable | Disable the extension | | relayWatcher.showOutputChannel | Show the output channel |

Release Notes

See CHANGELOG.md

Publish

Publish a new version:

  1. Update CHANGELOG.md and add a new version
  2. Publish with vsce
npm i -g vsce
vsce publish patch

FAQ

How does the extension work?

  • Activate if there are 1 or multiple relay.config.js file(s) within the workspace.
  • For each of the configuration files:
    • Check if relay-compiler is installed (if not, the configuration file gets ignored)
    • Check which package manager is installed by searching for a yarn.lock
    • Find the src, source directory

Potential Improvements

  • Use relay-config to support relay.config.json and package.json configurations (legacy)

Inspired by