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

azure-function-json-compiler

v0.1.0

Published

Add flexibility to Node Azure Function projects by automating the creation of function.json files!

Downloads

10

Readme

azure-function-json-compiler

Summary

This project aims to free developers from the folder constraints of a Node.js Azure Fuctions project. Currently, with Azure Functions, top level folders with function.json files are required, which can lead to medium sizes api projects becoming unweildly.

This CLI aims to resolve this issue by defining the function name, settings and function in a single js file, then extracting the function.json (and add a scriptFile reference) and name from the file on command. This command can be easily embedded in a deployment workflow.

Example file:

// path: src/users/get.az.js
const settings = {
  bindings: [
    {
      authLevel: "anonymous",
      type: "httpTrigger",
      direction: "in",
      name: "req",
      route: "users",
      methods: ["get"],
    },
    {
      type: "http",
      direction: "out",
      name: "$return",
    },
  ],
};

const name = "user_get";

const run = async (context, req) => ({ body: { user: "I am a user" } });

module.exports = { settings, name, run };

This example would generate a user_get folder, with a function.json file, with content:

{
  "bindings": [
    {
      "authLevel": "anonymous",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "route": "users",
      "methods": ["get"]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "$return"
    }
  ],
  "scriptFile": "../src/users/get.az.js
}

Installation

npm i -D azure-function-json-compiler

Commands

compile

The compile command generates the function.json files for a project.

Command Line Arguments

There are command line arguments for setting the names for the settings, and name variables.

  • -s: The name of the variable which contains the function.json content (optional)
  • -n: The name of the variable which is equal to the desired folder name (optional)

function.config.json

Configuration can be set using a function.config.json file, located in the project root. In this file, the glob pattern to azure function js files can be specified.

{
  "path": "src/**/*.az.js",
  "settings": "settings",
  "name": "name"
}

Default Values

Below are the default values for each of the arguments.

{
  "path": "src/**/*.az.js",
  "settings": "settings",
  "name": "name"
}

Limitations

This CLI does can not handle variable references, as such the name and settings variables must use literals.