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/autotool-plugin-turbo

v0.11.6

Published

My turbo config

Downloads

569

Readme

@alexaegis/autotool-plugin-turbo

npm ci codacy

Goal

The aim is to use a single, catch-all turbo.json config. This is hard because sometimes packages have unique dependencies. For example linting can be done without building the packages. Well, in a regular project yes but if your lint configuration itself is a local build artifact, that one has to be built first. This is a very unique requirement.

To achieve this while not modifying the root turbo.json config, your only option is (unless inverse dependencies become possible) placing an override turbo.json file into every single package.

Task postfixes

Tasks are postfixed with an _ so npm scripts that call turbo are clearly separated from the ones that contain the actual implementation of that script. This allows defining tasks inside the individial packages that call turbo filtering to that package only. You shouldn't use the internal task implementation of a package because that doesn't ensure that dependencies are met.

Notes

Why does lint:svelte depend on ^build?

svelte-check fails if types can't be resolved for an import, and local library export types are only available if the library is packaged. svelte-package generates the .svelte.d.ts files.

It is advised to only export ts files, and not svelte files becuase of this type related limitation, but this task dependency is there nontheless to avoid any possible weird errors during lint:svelte.