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

@unified-latex/unified-latex-util-pgfkeys

v1.8.1

Published

Functions for manipulating pgfkeys-like arguments in a unified-latex AST

Downloads

8,120

Readme

unified-latex-util-pgfkeys

What is this?

Functions to help manipulate unified-latex Abstract Syntax Tree (AST) that contain pgfkeys-style arguments. Note that pgfkeys aren't built into Ast.Ast. Instead, parsing nodes as pgfkeys will produce a new (incompatible) AST.

When should I use this?

If you want to parse or manipulate macros/environments with pgfkeys-style arguments.

Install

npm install @unified-latex/unified-latex-util-pgfkeys

This package contains both esm and commonjs exports. To explicitly access the esm export, import the .js file. To explicitly access the commonjs export, import the .cjs file.

Functions

createMatchers()

function createMatchers(): { isChar: (node: Ast.Node, char: string) => node is Ast.String; isComma: (node: Ast.Node) => node is Ast.String; isEquals: (node: Ast.Node) => node is Ast.String; isWhitespace: (node: Ast.Node) => node is Ast.Whitespace; isParbreak: (node: Ast.Node) => node is Ast.Parbreak; isSameLineComment: (node: Ast.Node) => boo...

parsePgfkeys(ast, options)

Parse the arguments of a Pgfkeys macro. The ast is expected to be a comma separated list of Items. Each item can have 0 or more item parts, which are separated by "=". If itemPart is undefined,

If options.allowParenGroups === true, then commas that occur inside groups of parenthesis will not be parsed as separators. This is useful for parsing tikz \foreach loops.

function parsePgfkeys(
  ast: Ast.Node[],
  options: { allowParenGroups: boolean }
): Item[];

Parameters

| Param | Type | | :------ | :-------------------------------- | | ast | Ast.Node[] | | options | Omitted |

pgfkeysArgToObject(arg)

Parse arg as pgfkeys and return a JavaScript object with the results. The keys will be normalized to strings and the values will be arrays of nodes.

function pgfkeysArgToObject(
  arg: Ast.Node[] | Ast.Argument
): Record<string, Ast.Node[]>;

Parameters

| Param | Type | | :---- | :--------------------------- | | arg | Ast.Node[] \| Ast.Argument |

Types

Item

export type Item = {
    itemParts?: Ast.Node[][];
    trailingComment: Ast.Comment | null;
    trailingComma?: boolean;
    leadingParbreak?: boolean;
};