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

@shopgate/extension-config-validator

v1.4.3

Published

## Install ```npm install @shopgate/extension-config-validator```

Downloads

195

Readme

Extension Config File Validator

Install

npm install @shopgate/extension-config-validator

Usage

To execute the validator pass it to the root folder you extension: $(npm bin)/extension-config-validator <path>

Alternative usage

You can add it to your package.json like this:

"scripts": {
 "validate": "extension-config-validator <path>"
}

Changelog

1.4.2

Fixed

  • validation of internal hooks' inputs/outputs for consistency

1.4.1

Added

  • component validation in validation command

1.4.0

Added

  • validation for component paths

1.3.0

Added

  • support for 'internal' inputs/outputs which are accessible only by steps of the respective extension

1.2.0

Fixed

  • add support for admin config type

1.1.4

Fixed

  • support key, keys and nothing on params of bigapi type
  • fixed unit tests

1.1.3

Changed

  • the field nameof an input or output within is now called key

1.1.2

Fixed

  • entrypoint
  • removed some error prone and not needed async processing

1.1.0

Added

  • validation for hook step definitions

1.0.4

Added

  • validation for step configurations
  • validation for component paths