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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@c0ldra1n/svelte-json-schema-form

v0.0.7-4

Published

## Howto

Readme

svelte-json-schema-form

Howto

Writing Custom Widgets

Importing widgets

When importing widgets, you must use the *(general import) identifier.

This is to access both the component itself and its metadata.

<script>
  import JSONSchemaForm from "@c0ldra1n/svelte-json-schema-form";
  import * as StringWidget from "./string-widget.svlete";
</script>

<JSONSchemaForm widgets="{[StringFormWidget]}" />

Priorities

Custom widgets have priorities over default widgets. Prioritiies within them are determined by the order they are inserted in.

Assigning widgets

It is important that a widget is instantiated from the correct, designated property. The following methods are used to "resolve" the widget from each properties.

If both type and resolveWidget are exported, the widget resolver code will first match for type, then execute resolveWidget.

Type

<script context="module">
  export const type = "string";
</script>

type could also be an array if it can support multiple types

<script context="module">
  export const type = ["integer", "number"];
</script>

shouldResolve

<script context="module">
  export const shouldResolve = (propertyID, schema) => {
      if(/*some condition*/){
          // the widget will be displayed.
          return true;
      }else{
          // the widget will not be displayed.
          return false;
      }
  }
</script>

Recursive widgets

It is possible to use the resolveWidgetfunction within a custom widget. Use getContext("@c0ldra1n/svelte-json-schema-form") to access the function.

<script>
  import { getContext } from "svelte";
  const { resolveWidget } = getContext("@c0ldra1n/svelte-json-schema-form");
</script>

A note about default

The default key in JSON schema is retained, but is renamed as defaultValue during property assignment.

When exporting properties from your custom widget, you should export defaultValue instead of default, as shown in the example below.

<script>
  export let defaultValue;
</script>