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

validated-parameters

v1.1.1

Published

Tools for extracting validated parameters from process.env and query strings

Downloads

12

Readme

Validated Parameters

This library simplifies the process of validating and converting string maps, such as query strings or environment variables, into well-typed data structures. It is particularly useful for quickly setting up a well-typed environment for your application.

Installation

npm install --save validated-parameters

Usage

Example: Azure Function HTTP Trigger

Here's an example of how to use validated-parameters to validate and convert query string parameters in an Azure Function HTTP trigger:

  1. Import the required functions and types:
import {
  getValidParameters,
  stringParameter,
  numberParameter,
  booleanParameter,
  optionally,
} from 'validated-parameters';
  1. Define the expected parameter map:
const parameterMap = {
  searchText: stringParameter(),
  page: numberParameter(),
  pageSize: numberParameter(),
  includeArchived: booleanParameter(),
};
  1. Use getValidParameters in your Azure Function:
import { AzureFunction, Context, HttpRequest } from '@azure/functions';

const httpTrigger: AzureFunction = async function (
  context: Context,
  req: HttpRequest
): Promise<void> {
  const { searchText, page, pageSize, includeArchived } = getValidParameters(parameterMap, req.query);

  // Your logic for handling the request with validated and converted parameters.
};

export default httpTrigger;

Setting up a Well-Typed Environment

validated-parameters can be used to create a well-typed environment for your application. In this example, we will set up a centralized, well-typed environment using environment variables:

  1. Create a file named environment.ts:
import {
  makeEnvironment,
  stringParameter,
  numberParameter,
  booleanParameter,
  optionally,
} from 'validated-parameters';

const environmentVariables = {
  DB_HOST: stringParameter(),
  DB_PORT: numberParameter(),
  DB_USER: stringParameter(),
  DB_PASSWORD: stringParameter(),
  ENABLE_CACHE: booleanParameter(),
  CACHE_EXPIRATION: optionally(numberParameter()),
};

export const environment = makeEnvironment(environmentVariables);
  1. Use the environment object in your application:
import { environment } from './environment';

console.log(environment.DB_HOST);
console.log(environment.DB_PORT);
console.log(environment.DB_USER);
console.log(environment.DB_PASSWORD);
console.log(environment.ENABLE_CACHE);
console.log(environment.CACHE_EXPIRATION);

The environment object provides well-typed access to environment variables, ensuring that your application always uses the correct data types.

Customization

validated-parameters also allows you to customize the validation and conversion process by providing optional configuration. For example:

const customParameterMap = {
  name: stringParameter({
    minLength: 2,
    maxLength: 100,
    onInvalid: (value) => console.warn(`Invalid name: ${value}`),
  }),
  age: numberParameter({
    min: 18,
    max: 120,
    onInvalid: (value) => console.warn(`Invalid age: ${value}`),
  }),
  isAlive: booleanParameter({
    onFailedToConvert: (value, error) => console.error(`Failed to convert isAlive: ${value}`, error),
  }),
  isHappy: optionally(booleanParameter()),
};