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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@tamagui/style-grammar

v3.0.18

Published

This package owns the shared parser and intermediate representation for Tamagui style value strings.

Readme

@tamagui/style-grammar

This package owns the shared parser and intermediate representation for Tamagui style value strings.

Runtime consumers must follow the repository's one-parse-per-unique-value constraint. Cache the parsed representation and extend it with structural predicates when a new consumer needs more information. Do not add a second string scanner beside the grammar.

The one scanner

scanFlatValue.ts is the split: one left-to-right pass that hands a handler index ranges and never allocates a slice. parseValue is built on it, and so are the three scanners in @tamagui/web (contributeStyleString, resolveVariants, hasFlatModifier). A consumer that needs a different answer writes a different handler, never a second pass.

The Rust LSP's tables are generated from here

code/lsp/crates/tamagui-grammar is an editor transport for this grammar and never a second owner of what a modifier means, so its modifier tables and its conformance vectors are generated:

bun run generate:rust   # write src/generated.rs and tests/vectors.json
bun run check:rust      # fail if what is on disk differs

checks.yaml runs check:rust and cargo test --workspace on every push. When you change a modifier name, an alias, a platform, or anything the parser decides, regenerate and commit both files with the change.