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-add-imports

v1.0.10

Published

add imports/requires if not already present with jscodeshift

Downloads

67,879

Readme

jscodeshift-add-imports

CircleCI Coverage Status semantic-release Commitizen friendly npm version

Easily add import and require statements with jscodeshift. If something is already imported, returns the locally bound identifier, and avoids name conflicts.

Usage

npm install --save jscodeshift-add-imports
const j = require('jscodeshift')
const addImports = require('jscodeshift-add-imports')

const { statement } = j.template

const code = `
// @flow
import {foo, type bar} from 'foo'
import baz from 'baz'
`

const root = j(code)
const result = addImports(root, [
  statement`import type {bar, baz} from 'foo'`,
  statement`import blah, {type qux} from 'qux'`,
])
console.log(result)
console.log(root.toSource())

Output code:

// @flow
import { foo, type bar } from 'foo'
import baz from 'baz'
import type { baz as baz1 } from 'foo'
import blah, { type qux } from 'qux'

Return value:

{
  bar: 'bar',
  baz: 'baz1',
  blah: 'blah',
  qux: 'qux',
}

Compatibility

Currently tested on [email protected] with the following parsers:

  • babylon
  • ts

There are currently issues with the babel and flow parsers.

It won't likely work with other custom parsers unless they output nodes in the same format as Babel for import declarations, variable declarations, require calls, and object patterns.

addImports(root, statments)

Arguments

root

The jscodeshift-wrapped AST of your source code

statements

The AST of an import declaration or variable declaration with requires to add, or an array of them.

Return value

An object where the key is the local identifier you requested in statements, and the value is the resulting local identifier used in the modified code (which could be the existing local identifier already imported in the code or the local identifier chosen to avoid name conflicts with an existing binding)