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

refaker-local-id

v0.1.0

Published

Download or fake JSON schemas from $ref values

Downloads

4

Readme

A JSON-schema $ref faker

Build Status NPM version Coverage Status

Inspired on json-schema-validator for JAVA, the --fakeroot option, actually.

This fork also allows non-standard references via "id".

If you're validating some RAML (like me) then you should validate your JSON-schemas and examples also.

For this purpose I'm using ramlev which is using tv4, but you're encouraged to download any $ref manually before validating.

Solution?

var tv4 = require('tv4'),
    refaker = require('refaker-local-id');

var data = { /* ... */ },
    schema = { /* ... */ };

refaker({
  schema: schema,
  fakeroot: 'http://example.com',
  directory: '/path/to/schemas'
}, function(err, refs, schemas) {
  if (err) {
    console.log(err);
  } else {
    for (var id in refs) {
      // register resolved refs
      tv4.addSchema(id, refs[id]);
    }

    // validates the first passed schema
    console.log(tv4.validateResult(data, schemas[0]));
  }
});

That's it.

Options

  • schema (object|aray)

    The JSON-schema to validate.

  • schemas (object|array)

    Multiple JSON-schemas to validate at once.

    This is an alias for the schema option.

  • fakeroot (string)

    If provided, any matching $ref will be resolved under the specified directory.

  • directory (string)

    A local path containing the JSON-schemas.

    If missing, will use process.cwd() instead.

  • timeout (number)

    Timeout when resolving remote schemas, default to 200ms.

Any $ref found will be downloaded or faked locally.

Callback

The given callback will receive three arguments:

  • err (mixed)

    Empty means success.

  • refs (object)

    Hash of resolved $refs.

  • schemas (array)

    Normalized schemas if success (same order as input).

Bitdeli Badge