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

parser36

v0.0.1

Published

r36s dts parser

Readme

parser36

A lightweight, dependency-free JavaScript library for parsing, manipulating, and reconstructing r36s dts files.

Overview

Parser36 provides a Proxy-based API that converts complex DTS structures into a manipulatable JavaScript object tree. This allows for programmatic modification of hardware descriptions before stringifying them back into a valid DTS format compatible with the Device Tree Compiler (dtc).

How it Works

1. Tokenization

The parser identifies DTS elements:

  • Comments (skipped)
  • Directives (e.g., /dts-v1/)
  • Labels and Node names
  • Properties (Strings, Cells <...>, Bytes [...])

2. AST Construction & Proxy Wrapper

The parseDTS(source) function returns a Proxy-wrapped root node.

  • Path Access: dts.get('/path/to/node')
  • Search: dts.find('compatible-string')
  • Native JS Values: Assign numbers, strings, or arrays directly.

3. Manipulation API

  • node.property = value: Update or create a property.
  • node.add(name, { props }): Inject new child nodes.
  • node.children: Iterate through child nodes.

4. Stringification

  • node.toString(): Reconstructs the tree into a clean, properly indented DTS file.

Example Usage

import { readFileSync, writeFileSync } from 'fs';
import { parseDTS } from './parser36.js';

const content = readFileSync('my_device.dts', 'utf8');
const dts = parseDTS(content);

// 1. Modify properties via path
const mmc = dts.get('/dwmmc@ff370000');
if (mmc) {
    mmc.status = 'okay';
    mmc['max-frequency'] = 150000000; // Auto-converts to <0x8f0d180>
}

// 2. Find and update a node by compatible
const panel = dts.find('simple-panel-dsi');
if (panel) {
    panel['dsi,flags'] = [0xe03];
}

// 3. Stringify back to DTS
writeFileSync('updated.dts', dts.toString());

Validation

The tests/test-md5.js script is provided to ensure the parser's stability. It performs a "round-trip" validation (DTS -> AST -> DTS) and verifies that the output remains functionally identical to the input.

Build & Test

Use the root Makefile to run everything:

make        # Patch examples and run tests
make clean  # Remove generated files