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

@tonyhallett/github-actions

v1.4.6

Published

Module for multiple github actions

Downloads

11

Readme

This contains github actions code to be used in github actions as well as notes on github actions. The actions have their own repositories solely due to the requirement for one action per repository for the marketplace. For typescript actions there is a repo template, note that this is for single action repositories. This template can be amended if you want a multi action repository. A multi action repository has a folder for each action containing a single action.yaml file with runs: main: the built script file.

Below is a script file that facilitates building with ncc in a repository with a naming convention. Every action folder should have a corresponding typescript file in src.

/* eslint-disable no-console */
import * as path from 'path'
import * as fs from 'fs'
import {exec} from 'child_process'

function getRootDirectory(): string {
  const scriptsDirectory = __dirname
  return getParentDirectory(scriptsDirectory)
}

function getSourceDirectory(): string {
  return path.join(getRootDirectory(), 'src')
}

function getSourceFiles(): string[] {
  const sourceDirectory = getSourceDirectory()
  return readDirSyncOfType(sourceDirectory, true)
}

function readDirSyncFullPath(directory: string): string[] {
  return fs.readdirSync(directory).map(fe => path.join(directory, fe))
}

function readDirSyncOfType(directory: string, files: boolean): string[] {
  const fileEntries = readDirSyncFullPath(directory)
  return fileEntries.filter(fe => {
    const isDirectory = fs.statSync(fe).isDirectory()
    return files ? !isDirectory : isDirectory
  })
}

function dirName(dir: string): string {
  return dir.split(path.sep).pop() as string
}

function getParentDirectory(dir: string): string {
  const parts = dir.split(path.sep)
  parts.pop()
  return parts.join(path.sep)
}

function nccBuildMultipleActionsByNamingConvention(): void {
  const sourceFiles = getSourceFiles()
  const possibleActionDirectories = readDirSyncOfType(
    getRootDirectory(),
    false
  ).map(d => dirName(d))
  for (const sourceFile of sourceFiles) {
    const matchingActionDirectoryName = path.basename(sourceFile, '.ts')
    if (
      possibleActionDirectories.some(d => d === matchingActionDirectoryName)
    ) {
      nccBuild(sourceFile)
    }
  }
}

function nccBuild(tsFile: string): void {
  console.log(`ncc building ${tsFile}`)
  const distFolder = path.basename(tsFile, '.ts')
  exec(
    `npm run nccSingle -- build ${tsFile} --source-map --license licenses.txt --out dist/${distFolder}`,
    {cwd: getSourceDirectory()},
    (err, stdout, stderr) => {
      if (err) {
        console.log(stderr)
      } else {
        console.log(stdout)
      }
    }
  )
}

nccBuildMultipleActionsByNamingConvention()

Amend the scripts key in package.json

"scripts": {
    "build": "tsc",
    "format": "prettier --write **/*.ts",
    "format-check": "prettier --check **/*.ts",
    "lint": "eslint src/**/*.ts",
    "test": "jest",
    "all": "npm run format && npm run lint && npm run package && npm test && npm run nccBuild",
    "nccBuild": "ts-node scripts/nccBuild.ts",
    "nccSingle": "ncc"
  },