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

import-runner

v1.23.0

Published

Low code control flow with dynamically imported functions

Downloads

27

Readme

👟 Import Runner

Low code control flow using dynamic imports

⚙️ Install

npm install import-runner

🏃 Run

Import runner provides a shorthand for executing complex control flows using dynamic imports:

import importRunner from "import-runner"

export default async (input: {
  someOption: boolean
}): Promise<any> => {
  return await importRunner({
    input,
    each: [
      import("./myFunction"),
      import("./thatFunction"),
      {
        all: [
          import("./otherFunction"),
          import("./andAnotherFunction"),
          {
            route: [
              import("./wowAnotherFunction"),
              import("./enoughFunction"),
            ],
          },
        ],
      },
    ],
  })
}

ℹ️ Import runner calls the default function of the dynamic import (export default)

ℹ️ If a function call returns an object, it is assigned to the final output (Object.assign)

| Option | Description | | :------ | :---------------------------------------------------------- | | input | Input object | | all | Concurrent execution | | each | Sequential execution | | route | Concurrent conditional execution (uses "or" on input types) |

🤖 Low code

Wait a second! What is up with the any output of the importRunner call? Did I just lose all my types? How do the child functions know what their inputs will be?

Because we have a somewhat formal structure, we can programmatically parse importRunner calls and generate input and output types for the runner function and its component functions.

Example code to process source files with chokidar, eslint, prettier, file-replacer, and fs-extra:

import chokidar from "chokidar"
import { ESLint } from "eslint"
import fileReplacer from "file-replacer"
import fsExtra from "fs-extra"
import prettier from "prettier"
import sourceProcessor from "import-runner/dist/cjs/sourceProcessor"

chokidar.watch("./**/*.ts").on("change", (event, path) => {
  sourceProcessor({
    eslint: new ESLint({ fix: true }),
    fileReplacer,
    fsExtra,
    path,
    prettier,
    srcRootPath: __dirname,
  })
})