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-catcode

v1.8.0

Published

Tools for manipulating unified-latex ASTs

Downloads

16,002

Readme

unified-latex-util-catcode

What is this?

Functions to identify regions of a unified-latex Abstract Syntax Tree (AST) that need to be reparsed because of different category codes. For example, regions between \makeatletter and \makeatother.

When should I use this?

If you need to identify regions of the AST that need to be reparsed.

Install

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

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

findExpl3AndAtLetterRegionsInArray(tree)

Find regions between \ExplSyntaxOn...\ExplSyntaxOff and \makeatletter...\makeatother. Returns an object containing regions where one or both syntax's apply.

function findExpl3AndAtLetterRegionsInArray(tree: Ast.Node[]): {
  explOnly: Region[];
  atLetterOnly: Region[];
  both: Region[];
};

Parameters

| Param | Type | | :---- | :----------- | | tree | Ast.Node[] |

findRegionInArray(tree, start, end)

Find all contiguous segments in the array that are between start and end blocks. The start and end are functions that determine when a region starts and ends.

function findRegionInArray(
  tree: Ast.Node[],
  start: (node: Ast.Node) => boolean,
  end: (node: Ast.Node) => boolean
): Region[];

Parameters

| Param | Type | | :---- | :---------------------------- | | tree | Ast.Node[] | | start | (node: Ast.Node) => boolean | | end | (node: Ast.Node) => boolean |

hasReparsableMacroNames(tree, allowedTokens)

Checks whether tree has a macro that could be reparsed given the allowedTokens but do not do any reparsing. This function can be used in auto-detection schemes to determine if macro names should actually be reparsed.

function hasReparsableMacroNames(
  tree: Ast.Ast,
  allowedTokens: string | Set<string>
): boolean;

Parameters

| Param | Type | | :------------ | :---------------------- | | tree | Ast.Ast | | allowedTokens | string \| Set<string> |

hasReparsableMacroNamesInArray(tree, allowedTokens)

Checks whether the array has a macro that could be reparsed given the allowedTokens but do not do any reparsing. This function can be used in auto-detection schemes to determine if macro names should actually be reparsed.

function hasReparsableMacroNamesInArray(
  tree: Ast.Node[],
  allowedTokens: Set<string>
): boolean;

Parameters

| Param | Type | | :------------ | :------------ | | tree | Ast.Node[] | | allowedTokens | Set<string> |

reparseExpl3AndAtLetterRegions(tree)

Find regions between \ExplSyntaxOn...\ExplSyntaxOff and \makeatletter...\makeatother and reparse their contents so that the relevant characters (e.g., @, _, and :) become part of the macro names.

function reparseExpl3AndAtLetterRegions(tree: Ast.Ast): void;

Parameters

| Param | Type | | :---- | :-------- | | tree | Ast.Ast |

reparseMacroNames(tree, allowedTokens)

Reparses all macro names so that they may optionally include characters listed in allowedTokens. This is used, for example, when parsing expl3 syntax which allows _ to be used in a macro name (even though _ is normally stops the parsing for a macro name). Thus, a macro \foo_bar:Nn would be parsed as having the name foo_bar:Nn rather than as foo followed by the strings _, bar, :, Nn.

function reparseMacroNames(
  tree: Ast.Ast,
  allowedTokens: string | Set<string>
): void;

Parameters

| Param | Type | | :------------ | :---------------------- | | tree | Ast.Ast | | allowedTokens | string \| Set<string> |

reparseMacroNamesInArray(tree, allowedTokens)

Reparses all macro names in the array so that they may optionally include characters listed in allowedTokens. This is used, for example, when parsing expl3 syntax which allows _ to be used in a macro name (even though _ is normally stops the parsing for a macro name).

function reparseMacroNamesInArray(
  tree: Ast.Node[],
  allowedTokens: Set<string>
): void;

Parameters

| Param | Type | | :------------ | :------------ | | tree | Ast.Node[] | | allowedTokens | Set<string> |