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

@launchtray/hatch-scim2-api

v0.21.0-alpha.55

Published

This project is a TypeScript API project that defines or generates an [OpenAPI Specification](https://swagger.io/specification/).

Downloads

8

Readme

hatch-scim2-api

This project is a TypeScript API project that defines or generates an OpenAPI Specification.

API projects such as this one are typically used as inputs to an auto-generated client and/or server SDK project, which are in turn often used by webapp projects to define and interact with HTTP-based APIs in a type-safe, consistent way.

Defining an OpenAPI specification using JSON or YAML directly can be cumbersome and error-prone. This project is meant to encapsulate the definition of an API, using tools to cut down on cumbersome boilerplate and assist with merging together multiple type and API definitions.

Specification formats

There are multiple formats that this project can use for defining an OpenAPI specification.

Spot

Optionally (and by default), this project can use a Spot file to define an OpenAPI specification. Spot uses a TypeScript-based DSL to define APIs with minimal boilerplate. Spot APIs can be generated by adding --spot [input-spot-file] to the build scripts in package.json.

YAML (or JSON)

This project can use raw YAML or JSON OpenAPI specification files as inputs. Note that since JSON or YAML APIs can be generated by adding --spec [input-spec-file]to the build scripts in package.json.

Combining formats

Multiple specification formats can be used in this project. The generator will merge outputs together as necessary. This is governed by the ordering of hatch-api arguments in the build and build:watch scripts in package.json. In the case of merge conflicts, the first argument precedence. For example, this command will allow definitions in api-overrides.yaml to override definitions in the api.ts Spot file:

hatch-api --spec src/api-overrides.yaml --spot src/api.ts

The above is the default used by this project: a Spot specification that can be overridden by a raw YAML OpenAPI specification.