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

ts-func

v0.3.0

Published

An engine to write Azure Function App function.json files as code.

Downloads

16

Readme

ts-func

Generate Azure Function App Configs from TypeScript and JavaScript!

Usage

Add a .tsfuncrc.ts file, and then use ts-func to compile and clean up generated function.json for your app.

> ts-func --help
usage: ts-func [-h] [-v] [cleanup | compile] ...

TS Func: Azure function.json generator

optional arguments:
  -h, --help           show this help message and exit
  -v, --version        show program's version number and exit

Commands:
  [cleanup | compile]
    cleanup            Clean up the current working directory of all emitted function.json.
    compile            Compile .tsfuncrc.(ts|js) in the current working directory and emit function.json.
~> ts-func compile --help
usage: ts-func compile [-h] [--noEmit] [--ignoreScripts]

optional arguments:
  -h, --help           show this help message and exit
  --noEmit, -n         Do not make any changes to the target directory.
  --ignoreScripts, -i  Ignore `scriptFile` properties; passes them unmodified to the output json.

How it works

Define a JavaScript or TypeScript file at the root of your project named .tsfuncrc; can be either .js or .ts.

This file is the configuration entry point for generating folders and function.json files in the root of the current working directory with a scheme of <EXPORT_NAME>/function.json. Function configurations must be named exports of either an object implementing AzureFunctionSchema or a function which returns AzureFunctionSchema object. Function exports may be either synchronous or async, they'll be await-ed either way.

Additional options may be passed to ts-func by exporting a default object with the options defined as desired. These options will be merged with the internal defaults and used when generating the Function App configurations. The options must be either export default in TypeScript, or explicitly named default in JavaScript in order to be picked up and not treated like a function configuration.

This config file is usable code; you can do anything you want, including importing the Azure Function Schema objects from other files and entry points, so long as the desired exports are named and follow the criteria outlined above.

See the sample .tsfuncrc.ts in the root of this project for inspiration.

Requires Node v12 or better.