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

optional-chaining-codemod

v1.7.0

Published

Codemod to migrate from Lodash get and logical and expressions to optional chaining

Downloads

30,383

Readme

Optional chaining codemod

Build Status npm version PRs Welcome

This is a codemod to migrate different types of lodash get calls and a && a.b kind of expressions to use optional chaining and nullish coalescing instead.

Following babel plugins are required to transpile optional chaining and nullish coalescing:

What it does?

  • a && a.b becomes a?.b
  • _.get(foo, 'a.b') and _.get(foo, ['a', 'b']) becomes foo?.a?.b
  • _.get(foo, 'a.b', defaultValue) becomes foo?.a?.b ?? defaultValue

You can check out the __textfixtures__ folder to see full list of supported transformations.

Why should I migrate to use optional chaining?

  • When using static type checkers like Flow or Typescript, optional chaining provides much better type safety than lodash get. Optional chaining is standard Javascript feature.
  • It also has a neater syntax than chaining && expressions one after another.

Install

$ yarn global add optional-chaining-codemod

or

$ npm install -g optional-chaining-codemod

Usage

$ optional-chaining-codemod ./**/*.js --ignore-pattern="**/node_modules/**"

with flow parser:

$ optional-chaining-codemod ./**/*.js --ignore-pattern="**/node_modules/**" --parser=flow

with typescript parser:

$ optional-chaining-codemod ./**/*.ts --ignore-pattern="**/node_modules/**" --parser=ts

with typescript+react parser:

$ optional-chaining-codemod ./**/*.tsx --parser=tsx

The CLI is the same as in jscodeshift except you can omit the transform file.

Alternatively, you can run the codemod using jscodeshift as follows:

$ yarn global add jscodeshift
$ yarn add optional-chaining-codemod
$ jscodeshift -t node_modules/optional-chaining-codemod/transform.js --ignore-pattern="**/node_modules/**" ./**/*.js

flags

This codemod has two flags:

  1. --skipVariables to skip variables passed to lodash get
  2. --skipTemplateStrings to skip template strings passed to lodash get

Especially the first case is risky as the variable might actually be something like var bar = "a.b.c" and produce from _.get(foo, bar) following: foo?[bar] although lodash would treat it like foo?.a?.b?.c".

Contributing

Contributions are more than welcome! One area of improvement could be e.g better CLI or finding out new areas to migrate to use optional chaining.