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

unist-util-position

v5.0.0

Published

unist utility to get the position of a node

Downloads

30,084,336

Readme

unist-util-position

Build Coverage Downloads Size Sponsors Backers Chat

unist utility to get positional info of nodes.

Contents

What is this?

This utility helps with accessing positional info on a potentially dirty tree.

When should I use this?

The positional info is typically consistent and proper in unist trees generated by our ecosystem, but, user plugins could mess that up. If you’re making a reusable plugin, and accessing the positional info often, you might want to guard against that by using this utility.

You might also find the utility unist-util-generated useful to check whether a node is considered to be generated (not in the original input file).

You might also enjoy unist-util-stringify-position when you want to display positional info to users.

Install

This package is ESM only. In Node.js (version 16+), install with npm:

npm install unist-util-position

In Deno with esm.sh:

import {pointEnd, pointStart, position} from 'https://esm.sh/unist-util-position@5'

In browsers with esm.sh:

<script type="module">
  import {pointEnd, pointStart, position} from 'https://esm.sh/unist-util-position@5?bundle'
</script>

Use

import {fromMarkdown} from 'mdast-util-from-markdown'
import {pointEnd, pointStart, position} from 'unist-util-position'

const tree = fromMarkdown('# foo\n\n* bar\n')

console.log(position(tree))
console.log(pointStart(tree))
console.log(pointEnd(tree))

Yields:

{start: {line: 1, column: 1, offset: 0}, end: {line: 4, column: 1, offset: 13}}
{line: 1, column: 1, offset: 0}
{line: 4, column: 1, offset: 13}

API

This package exports the identifiers pointEnd, pointStart, and position. There is no default export.

position(node)

Get the positional info of node.

Parameters
  • node (Node) — node
Returns

Position, if valid (Position or undefined).

pointEnd(node)

Get the ending point of node.

Parameters
  • node (Node) — node
Returns

Point, if valid (Point or undefined).

pointStart(node)

Get the starting point of node.

Parameters
  • node (Node) — node
Returns

Point, if valid (Point or undefined).

Types

This package is fully typed with TypeScript. It exports no additional types.

Compatibility

Projects maintained by the unified collective are compatible with maintained versions of Node.js.

When we cut a new major release, we drop support for unmaintained versions of Node. This means we try to keep the current release line, unist-util-position@^5, compatible with Node.js 16.

Related

Contribute

See contributing.md in syntax-tree/.github for ways to get started. See support.md for ways to get help.

This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.

License

MIT © Titus Wormer