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

rehype-parse-isomorphic

v1.0.0

Published

A module that exports rehype-parse for Node.js and rehype-dom-parse for the browser.

Downloads

110

Readme

Install

$ npm i rehype-parse-isomorphic

Usage

Use just like rehype-parse and rehype-dom-parse.

[!WARNING]

The two libraries do not have exactly the same options. Make sure you account for the differences when the library is used in Node.js vs the browser.

Why?

It's better to use rehype-dom-parse than rehype-parse in the browser because the former has a significantly smaller bundle size (~8 kB vs ~63 kB).

Typically it's possible to just import rehype-parse in Node.js and rehype-dom-parse in the browser, but not always. Sometimes you want to parse HTML in code that can be used in either the browser or Node.js (i.e. in isomorphic code). Which library would you import in that code?

Without this module you'd be forced to import the lowest common denominator, the library that works in both Node.js and the browser, which would be rehype-parse. And now your browser JavaScript bundle is ~55 kB bigger than it should have been! With this module, you use the right library in each environment.

Contributing

Stars are always welcome!

For bugs and feature requests, please create an issue.

For pull requests, please read the contributing guidelines.

License

Apache License 2.0

This is not an official Google product.