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

@alexaegis/turbowatch

v0.12.0

Published

A turbowatch configuration to watch local dependencies through node_modules

Downloads

132

Readme

@alexaegis/turbowatch

npm ci codacy

Holds a configuration for turbowatch to watch local dependencies changing through node_modules.

It will first run buildDependenciesScript, then after that's finished the first time, it will run devScript.

Turbowatch configuration example

apps/my-app/dev.js

import { turbowatchLocalNodeModules } from '@alexaegis/turbowatch';
import { watch } from 'turbowatch';

void (async () => {
  await watch(
    await turbowatchLocalNodeModules({
      buildDependenciesScript: 'build:dependencies',
      devScript: 'dev_',
    }),
  );
})();

It's using an IIFE because turbowatch does not understand top-level awaits

Turbo example

When using with turbo, it's important that turbo cannot invoke itself. (In older versions of turbo it was allowed but worked wonky, since then it's actively prohibited) So when starting your app, start the invokation from turbowatch

apps/my-app/package.json

{
  "scripts": {
    "build:dependencies": "turbo run build-lib_ --filter my-app",
    "dev": "turbowatch dev.js",
    "dev_": "vite"
  }
}

And then the interesting part of a turbo.json. For the turbowatch setup specifically, only the build-lib_ task is used. Since turbowatch through the "build:dependencies" npm script already takes care of building the dependencies of the app, there's no need to start the app through turbo. For a more comprehensive turbo.json file, check the one in this package's repository.

turbo.json

{
  "$schema": "https://turborepo.org/schema.json",
  "tasks": {
    "build-app_": {
      "dependsOn": ["^build-lib_"],
      "outputs": ["dist/**"]
    },
    "build-lib_": {
      "dependsOn": ["^build-lib_"],
      "outputs": ["dist/**"]
    },
    "dev_": {
      "cache": false,
      "dependsOn": ["^build-lib_"],
      "persistent": true
    }
  }
}

I'm using separate build tasks for apps and libs, so I can skip building the app when I'm running turbo run build-lib_ --filter my-app, if they'd use the same script, the app would get built every time a dependency changes.

You then start your app using the "dev" script. You can put one in your root package.json too, but do not forget that you can't use turbo for this!

package.json

{
  "script": {
    "dev": "pnpm run --dir apps/my-app dev"
  }
}