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

slim-dom

v1.0.1

Published

Slim document object model based on the DOM & CSSOM.

Downloads

4

Readme

Slim document object model based on the DOM & CSSOM.

Goals

  • Subset of the DOM, but without mutability
  • Should be runnable over a network (web workers, AWS lambda, Node)
  • POJO data types
  • Ability to target other rendering engines (Canvas, Browserstack)

Basic example

const * as sdvm from "sdvm";
const * as pc from "paperclip";

// document is a POJO object. VM provided by language libraries
const document = await pc.loadVMDocument("./entry.pc");

const mount = document.createElement("div");
let renderResult = sdvm.renderers.dom.render(document, mount);

// later on...
const document2 = await pc.loadVMDocument("./entry.pc");

const diffs = sdvm.diffDocument(document, document2);
let renderResult = sdvm.renderers.dom.patch(diffs, mount);

const computedInfo = sdvm.renderers.dom.computeInfo(renderResult); // { rects: {}, computedStyles: {} }

const elementRect = getClientRect(element.hash, computedInfo);

Types

VMSource

type Position = {
  line: number;
  character: number;
  offset: number;
};

type Range = {
  start: Position;
  end: Position;
};

type VMObjectSource = {
  uri: string; // source file of object source
  kind: any; // kind of source object - usually expression type
  range: Range; // where the object is in the source file
};
VMObject
type VMObject = {
  source: VMObjectSource;
  type: string;
};
Node
type Node = {
} & VMObjct;
ParentNode
type ParentNode = {
  childNodes: Node[]
} & Node;
Element

type Attribute = {
  key: string;
  value?: string;
} & VMObject;

type Element = {
  shadow?: ParentNode;
  attributes: Attribute[];
} & ParentNode;
Document

Shape:

type Document =  {
  
} & Element;

StyleSheet

type StyleSheet = {
  rules: StyleRule[]
};

StyleRule

type StyleRule = {

}

MediaRule

TODO

UnknownRule

TODO

API

querySelector(element, query);
querySelectorAll(element, query);
getStyleSheets(element)
getElementSlots(element)

Reversed tag names

slot
style