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 🙏

© 2021 – Pkg Stats / Ryan Hefner

jscodeshift-paths-in-range

v1.1.0

Published

jscodeshift filter for paths in a given source code range

Downloads

30

Readme

jscodeshift-paths-in-range

CircleCI Coverage Status semantic-release Commitizen friendly npm version

A predicate for jscodeshift Collection.filter that only includes paths in the given source code range. This is for building IDE codemod extensions that operate on the selected code/cursor position in an editor.

More specifically:

  • If any paths are wholly contained within the range, use them (but not paths inside them)
  • Otherwise, pick the topmost node that fully contains the range

pathsInRange(start: number, end: number = start)

import pathsInRange from 'jscodeshift-paths-in-range'

Returns a predicate for Collection.filter.

Arguments

  • start - the index of the start of the range within the source code
  • end - the index of the end of the range within the source code (defaults to start)

Example

import jscodeshift from 'jscodeshift'
import pathsInRange from 'jscodeshift-paths-in-range'
const j = jscodeshift.withParser('babylon')

// editor is an example interface to a text editor in an IDE.
j(editor.getText())
  .find(j.ArrowFunctionExpression)
  .filter(
    pathsInRange(editor.getSelectedRange().start, editor.getSelectedRange().end)
  )
  .forEach(path => console.log(path.node))

pathsIntersectingRange(start: number, end: number = start)

The only difference between this and pathsInRange is it will include nodes that extend beyond start or end.

import pathsIntersectingRange from 'jscodeshift-paths-in-range'

Returns a predicate for Collection.filter.

Arguments

  • start - the index of the start of the range within the source code
  • end - the index of the end of the range within the source code (defaults to start)