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

react-query-selector

v1.5.1

Published

React Component selector engine. Provides a `querySelectorAll` type interface for React components rendered into a particular tree.

Downloads

24

Readme

react-query-selector

React Component selector engine. Provides a querySelectorAll type interface for React components rendered into a particular tree.

What is this for?

This is designed for development-time implementations only, primarily for react component aware integration testing. It relies on the React Developer tool hooks as well as non-minimized component names. As such it does not take efforts to be high performance or production-level page weight. This closely ties to the internal react implementation and may see breakages on react version upgades.

Basically under no circumstances should this be loaded in a production environment!

Selector Format

Selectors here are a superset of CSS selectors. Most selectors supported by css-select should work. The format is extended slightly to allod for <ReactComponent> in the place of a tag selector. This can be treated as if it were a tag selector and combined with other selectors, i.e. <MyComponent>[prop=1] would select components whose JSX representation matches the following <MyComponent prop="1" ... />.

When the final target is a <ReactComponent>, the return value will be the instance of the given react component. For DOM nodes the specific DOM node instance will be returned.

When doing a property selector, all component properties will be run through toString, which could lead to unexpected behavior on objects passed as properties.

Examples

ReactSelect.querySelector('<MyComponent> div');

API

  • querySelector(selector, [scope]) -> ReactComponent|DOMNode Returns the first react component or dom node matching the given selector. May optionally be scoped to a given react component or DOM node.
  • querySelectorAll(selector, [scope]) -> Array[ReactComponent|DOMNode] Returns all react components or dom nodes matching the given selector. May optionally be scoped to a given react component or DOM node.
  • componentDOMNodes(reactComponent) -> Array[DOMNode] Returns the root-level DOM nodes that a given react component renders to.
  • generatePath(DOMNode) -> string Returns a react selector that can be used to identify the give
  • dumpTree([scope]) -> [string] Returns simplified representation of the entire react render tree or optional sub-scopes

Getting started

npm run dev builds the library, then keeps rebuilding it whenever the source files change using rollup-watch.

npm test builds the library, then tests it.

License

MIT.