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

@diez/compiler

v10.0.0-beta.4

Published

The Diez compiler and related functionality.

Downloads

23

Readme

@diez/compiler

This package provides base classes which can be used to build compilers from Diez components into any target language, framework, or platform. A dependency on @diez/compile registers the CLI command diez compile --target <target-name>, which compiles components exported by such a package for a given compiler target (e.g. ios, android, or web) into the build directory.

The compiler itself has very few requirements; it is expecting to be run against a TypeScript project of this approximate shape:

project-root
├── package.json
├── src
│   └── index.ts
└── tsconfig.json

Additionally, the compiler expects the TypeScript configuration is set up to compile from src/ to lib/, and that the main file of the module is located at lib/index.js after compilation. This constraint may be loosened in the future, but for now, diez create sets up a project with this structure for you.

At compile time, the compiler first parses the TypeScript AST of every component exported in src/index.ts, and recursively parses its component properties. For example, given these contents:

import {Color} from '@diez/prefabs';

class Palette {
  red = Color.rgb(255, 0, 0);
}

export class DesignSystem {
  palette = new Palette();
}

the compiler will build a typed, abstract tree based on the exported component DesignSystem. Because Color and Palette are recursive dependencies of DesignSystem, they will also be processed. The resulting abstract tree will be emitted to the target compiler implementation to produce source code for the target platform, allowing you to to attach to a DesignSystem in a host code base.

For some examples of target compilers which can be built using @diez/compiler as a foundation, refer to @diez/targets.