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

@dotbox/compiler

v1.0.2

Published

A library for compiling DotBox files.

Downloads

4

Readme

@dotbox/compiler

Compiler infrastructure for DotBox.

Installation

# Using npm.
npm install @dotbox/compiler

# Using yarn.
yarn add @dotbox/compiler

Usage

compile(input: string)

The easiest way to use the DotBox compiler is to call the compile function with the text of your .box file.

import { compile } from "@dotbox/compiler";

const text = `
// This is my awesome DotBox file.
my_key = {
	my_number = 1_000
}
`;

const { value, error } = compile(text);

if (error) {
	// Handle compilation errors
	for (const err of error) {
		// ...
	}
} else {
	// Use `value` somehow
	console.log(value.my_key.my_number);
}

class Compiler

The compiler class can be accessed directly. This can be useful if you intend to compile multiple files and want to reuse a compiler instance for each one.

import { Compiler } from "@dotbox/compiler";

const text = `
// This is my awesome DotBox file.
my_key = {
	my_number = 1_000
}
`;

const otherText = `
// This is my _other_ DotBox file.
something? = false
`;

const compiler = new Compiler();

compiler.compile(text);

const firstResult = compiler.result;
const firstErrors = compiler.errors;

compiler.compile(otherText);

const secondResult = compiler.result;
const secondErrors = compiler.errors;

class Parser

If you intend to work with an AST representation of a DotBox file, the Parser class can be used.

import { Parser } from "@dotbox/compiler";

const text = `
// This is my awesome DotBox file.
my_key = {
	my_number = 1_000
}
`;

const parser = new Parser(text);

const ast = parser.parse();
const parserErrors = parser.errors;
const lexerErrors = parser.lexer.errors;

class Lexer

If you want to work with the raw tokens from a DotBox file, the Lexer class can be used.

import {
	Lexer,
	AnyToken,
	TokenType,
	Token,
	IdentToken,
	BoolToken,
	MissingToken,
} from "@dotbox/compiler";

const text = `
// This is my awesome DotBox file.
my_key = {
	my_number = 1_000
}
`;

const lexer = new Lexer(text);

const firstToken: Token = lexer.lex(AnyToken);
const maybeSecondToken: IdentToken | MissingToken = lexer.tryLex(
	TokenType.Ident
);
const missingToken: BoolToken | MissingToken = lexer.lex(TokenType.Bool);

A useful pattern for getting all the tokens of a file is to loop, waiting for an EOF token.

const tokens: Array<Token> = [];

let token: Token;
while ((token = lexer.lex(AnyToken)) && token.type !== TokenType.EOF) {
	tokens.push(token);
}