</>PackageGraphPackageGraph

resq

npmv1.11.0

React Element Selector Query (resq) - Query React components and children by selector (component name)

Not recommended for new projects

No — resq should not be adopted for new projects. Last published 1336 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1336 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package, about 35 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding resq to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

35 KB
Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing resq, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the resq README.

typescriptFull README ↗
interface RESQNode {
    name: 'MyComponent',
    node: HTMLElement | null,
    isFragment: boolean,
    state: string | boolean | any[] | {},
    props: {},
    children: RESQNode[]
}

resq$(selector: string, element?: HTMLElement): RESQNode
resq$$(selector: string, element?: HTMLElement): Array<RESQNode>

resq vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
resqthis page01MIT3 years ago
react152.8M82MIT1 day ago
react-dom143.7M47MIT1 day ago
react-style-singleton59.1M2MIT1 day ago
reselect44M1MIT1 day ago
next40.6M0MIT1 day ago

Dependencies

Declared by resq v1.11.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (16)

@babel/cli 7.2.3@babel/core 7.4.0@babel/plugin-transform-runtime 7.4.0@babel/preset-env 7.4.1@babel/runtime ^7.4.2babel-eslint 10.0.1babel-jest 24.5.0babel-loader ^8.0.6codecov ^3.3.0eslint 5.15.3eslint-plugin-jest 22.4.1jest 24.5.0npm-run-all 4.1.5rimraf ^2.6.3webpack ^4.29.6webpack-cli ^3.3.0

Used by

Popular packages that depend on resq.

Relationship graph

Dependencies (left) and dependents (right) of resq.

fast-deep-equalwebdriverioresq
resq dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 33 days apart.

Recent versions of resq
VersionPublishedSizeLicense
1.11.0latest3 years ago23 KBMIT
1.10.24 years ago23 KBMIT
1.10.15 years ago23 KBMIT
1.10.05 years ago21 KBMIT
1.9.25 years ago21 KBMIT
1.9.15 years ago21 KBMIT
1.9.05 years ago21 KBMIT
1.8.06 years ago20 KBMIT
1.7.16 years ago20 KBMIT
1.8.0-beta.06 years ago14 KBMIT
1.7.06 years ago14 KBMIT
1.6.17 years ago15 KBMIT
1.6.07 years ago15 KBMIT
1.5.07 years ago11 KBMIT
1.5.0-beta.07 years ago11 KBMIT

Overview

resq is an npm package that react Element Selector Query (resq) - Query React components and children by selector (component name). It has 1 known dependents in the graph. The latest version is 1.11.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need react Element Selector Query (resq) - Query React components and children by selector (component name) and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • Large dependency tree (17 direct dependencies) increases install size and audit surface.
  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use resq?

No — resq should not be adopted for new projects. Last published 1336 days ago.

How do I install resq?

Run `npm install resq` to add resq to your npm project.

How many dependencies does resq have?

resq declares 17 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 35 KB on disk.

What license is resq released under?

resq is distributed under the MIT license.

How popular is resq?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on resq.

Is resq still maintained?

The most recent release of resq (v1.11.0) was published 3 years ago.

Does resq run install scripts?

No. resq does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.