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

@touchtribe/frontend-scripts

v1.0.2

Published

Frontend build scripts to make your life easier

Downloads

103

Readme

Installation

Adding the package

npm install @touchtribe/frontend-scripts

Adding the CLI commands

In package.json:

{
  ...,
  "scripts": {
    "build": "frontend-scripts build",
    "watch": "frontend-scripts watch",
    "release": "frontend-scripts release",
  },
  ...
}

Adding tasks

frontend-scripts reads tasks out of the package.json file:

{
  ...,
  "frontend": {
    "sourcePath": "./src",
    "buildPath": "./dist",
    "tasks": []
  },
  ...
}

Environment specific tasks

To have environment specific build tasks, add them according to the index frontend.<environment>:

{
  ...,
  "frontend": {
    "sourcePath": "./src"
  },
  "frontend.development": {
    "buildPath": "./dist",
    "tasks": []
  },
  "frontend.production": {
    "buildPath": "./release",
    "tasks": []
  },
  ...
}

The resulting configuration is a merge of:

  • Base task config
  • frontend
  • frontend.environment (if it exists)

Tasks

Tasks get added using the following signature:

// taskname: string
// config: configuration object, will deep-merge the base config
[<taskname>, <config>]

Environment-specific tasks do not merge with global tasks but are added as separate tasks.

Task configuration

Todo

  • [x] Publish on NPM ;-)
  • [ ] Migrate documentation
  • [ ] Complete documentation
  • [ ] Rewrite task runner to single process
  • [ ] Move tasks to seperate modules