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

@cloudcannon/configuration-types

v0.0.16

Published

Contains TypeScript declarations and generates JSONSchema files for the CloudCannon configuration file.

Downloads

115

Readme

Configuration types

Contains TypeScript declarations and generates JSONSchema files for the CloudCannon configuration file.



Installation

npm i -D @cloudcannon/configuration-types

Usage

The primary use of this package is to validate your configuration file. You can also use it to autocomplete and read inline documention while editing. Here are some suggested workflows below.

YAML and JSON

We plan to add the configuration schema to JSON Schema Store, which would automatically enable in-editor validation, autocomplete and tooltips with the YAML or JSON LSP enabled.

Alternatively, you can add a comment to the top of your file to use a specific schema for YAML files:

# yaml-language-server: $schema=https://raw.githubusercontent.com/CloudCannon/configuration-types/main/build/cloudcannon-config.json

collections_config:
  posts:
    name: Blog
    icon: event

Or the top-level $schema entry for JSON files:

{
  "$schema": "https://raw.githubusercontent.com/CloudCannon/configuration-types/main/build/cloudcannon-config.json",

  "collections_config": {
    "posts": {
      "name": "Blog",
      "icon": "event"
    }
  }
}

You could also/alternatively validate the file on the command line with something like ajv-cli:

npm i @cloudcannon/configuration-types ajv-cli
npm run ajv validate -s node_modules/@cloudcannon/configuration-types/cloudcannon-config.json -d cloudcannon.config.yml

JavaScript

For a CommonJS formatted configuration file (e.g. /cloudcannon.config.cjs), you can use a JSDoc comment to indicate the type of the module export:

/** @type {import("@cloudcannon/configuration-types").Configuration} */
const config = {
  collections_config: {
    posts: {
      name: 'Blog',
      icon: 'event',
    },
  },
};

module.exports = config;

Then use the TypeScript LSP in your supported editor, ensuring it is set up to check JavaScript files. This would provide in-editor validation, autocomplete and tooltips as you modify the file.

You could also/alternatively run tsc over your file to validate there are no issues outside of your editor:

npx tsc test/cloudcannon.config.js --allowJs --checkJs --noEmit

Development

Install dependencies:

npm i

Build JSONSchema files:

npm run build

License

MIT