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 🙏

© 2025 – Pkg Stats / Ryan Hefner

remark-obsidious

v0.9.9

Published

remark-obsidious: A strict TypeScript-powered remark plugin for transforming Obsidian-flavored Markdown. Builds a file tree & lookup table while handling callouts, embeds, and internal links—perfect for static sites using raw vault files.

Downloads

29

Readme

silly AI generated image of an obsidian crystal with magic-ish veins of gold connecting various parts together similar to a graph image

🚨 Not ready for use 🚨

Let me dogfood this beast for a bit before you try to use it in anything you care about.
I anticipate that I'll be making heavy changes as I get a feel for what works and what doesn't in the near future


[!CAUTION] Seriously, do not use this! Until I ship a 1.0.0 release I reserve the right to change any thing at any time 😜

Latest build info:

  • @latest build version is: 0.9.9

project goals

  1. provide a remark plugin which will transform MDASTs that have Obsidian flavored features into a structured format.
  2. provide a script which will walk an Obsidian vault and index it
  3. provide a vault interface which exposes the following:
    • a filetree representation of the vault items
    • a lookup table organized by id for the vault items
    • some utility methods for working with the vault items

Tasks

remark-obsidious plugin features:
  • [x] ==hilight text==
  • [x] [[internal links]] with roll-over previews
  • [x] [[internal link | with alias]]
  • [x] [[internal link#heading-anchor]]
  • [x] [[internal link#heading| alias]]
  • [x] ![[embed images]]
  • [x] ![[embedded markdown]]
  • [x] ![[embedded markdown#heading]]
  • [x] [!callout] Title
    • with [!nested_callouts] Nested Callouts

obsidious vault indexing script
  • [x] should be able to set an in path
  • [x] should be able to set an out path
  • [x] should be able to override the default index name
  • [x] should be able to use a .gitignore file ask a mask
  • [x] should know what image files are supported by the vault
    • (avif,bmp,gif,jpeg,jpg,png,svg,webp) per https://help.obsidian.md/file-formats
  • [x] should have a version which matches the npm package semantic version
  • [ ] should probably run under node LTS - (I'm currently on v23 😜)

ObsidiousVault Interface
  • [x] VaultItems should have the following meta:
    • filepath: (relative path from --in to file)
    • fileType: file or folder
    • id: a unique ID sha hash based on the filepath
    • label: the file's name recorded in the "obsidian" fashion
      • markdown file names are filename no extension
      • all other files are filename.extension
    • mtimeMs: last time the file was modified
  • [x] VaultFileTree nodes should have
    • children array of child nodes
    • id vault item hash
    • label the vault item label
  • [x] VaultInterface should have
    • files a record of vault items organized by id
    • fileTree the generated filetree
    • idsByExtension a lookup table of vault item ids by extension type
    • idsByLabelSlug lookup table of vault item ids by sluggified vault labels
    • idsByWebPath lookup table of vault item ids by "webPath"s
    • imageIds a list of all the ids where the extension was a recognized obsidian image type
    • stats some stats about the vault

Final items before 1.0.0
  • [x] Add basic test coverage
  • [ ] dogfood this in another app and tweak accordingly
  • [ ] Write some documentation / Getting started guides
  • [ ] fix the bugs I didn't catch during the previous two rounds

Feature creep / future ideas
  • [ ] maybe include semantic-release so i don't have deal with it
  • [ ] add github deployment strat
  • [ ] add support for symlinks
  • [ ] consider adding total vault filesize to stats
  • [ ] consider the value of adding filesize for vaultItems vs increased index size
  • [ ] MDX support?
  • [ ] consider some ~~excuses~~ ideas for remark redirective usage