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

@uwu/treetype

v1.1.1

Published

Convert types into module declarations

Downloads

41

Readme

TreeType

TreeType generates module definitions for object types.

Install

npm    i -D @uwu/treetype
yarn add -D @uwu/treetype
pnpm add -D @uwu/treetype

Usage

treetype <definition file> [output file]

If the output file is not specified, standard output is used.

The definition file specifies which modules to generate, the format is as follows:

## These directives control some global options
# `source` specifies which file should be used as the source of all source types
\source ./types.ts
# `import` specifies how `source` should be imported in the generated file
\import ./types

# All top-level modules must have a source type, this source type must be exported
# All properties on the source type are declared exports on the generated module
@module from SourceType {
  # You may further specify a property inside a module to generate nested modules
  test
  hello {
    world
    foo
  }
  # You may override the source type for a portion of the module tree, this property should not exist on the parent source type
  bar from AnotherType
  baz from EvenMoreTypes {
    hello
    world
  }
}

Should any path or tree node need to contain whitespace, you can enclose it in quotes (").

Bundler usage

A bundler plugin will be provided in the future, until then, here are examples of how to use a bundler to make TreeType modules usable

Rollup

export default {
	output: {
		globals(id) {
			if (id.startsWith("@module")) return id.substring(1).replace(/\//g, ".");
		},
	},
};