Upgrade babel-plugin-emotion's touch dependency to ^2.0.1

[mtzhang]

• emotion version: 9.1.2
• react version: 16.2.0

Relevant code.

emotion/packages/babel-plugin-emotion/package.json

Line 24 in d882e8b

"touch": "^1.0.0"

emotion/packages/babel-plugin-emotion/src/index.js

Line 6 in d882e8b

import { touchSync } from 'touch'

emotion/packages/babel-plugin-emotion/src/index.js

Line 580 in d882e8b

touchSync(cssFileOnDisk)

What you did:
Within my project makefile

$ npm install
$ touch node_modules

What happened / Problem description:

$ npm install
$ touch node_modules
bad touch!
/Users/mzhang1/Documents/dev/node_modules/touch/bin/touch.js:28
      throw er
      ^

Error: EISDIR: illegal operation on a directory, open 'node_modules'
    at Error (native)

I'm using react-select in a project, which in turn is using emotion. I'm running into a problem with builds because of emotion's outdated dependency (specifically within babel-package-emotion) on touch.

During my project build, the $PATH variable is prepended with node_modules/.bin, so local executables can be conveniently used in the Makefile. Because it's prepended, the touch dependency takes precedence over the system touch, and because the older version of this library doesn't work with directories, builds are failing.

Suggested solution:

Changing the $PATH to append node_modules/.bin to $PATH, as opposed to prepending it, is not a solution for my project, and so my suggested solution is to

update the touch dependency to at least v2.0.1.

This is because the name of the CLI installed by the package was changed from touch.js to nodetouch.js in v2.0.0 (commit), with a small correction to the bin file name in v2.0.1 (commit). This will eliminate the problem of the same-named dependency.

For additional context, a similar request to upgrade touch was made to nodemon in July 2017 – see the following issue: remy/nodemon#1072.

[Andarist]

Would you like to create a PR for this?

[mtzhang]

@Andarist Here it is! #866

PR template asks me to do the following, but I suspect I do not have permissions to do so:

<!-- Please add a `Tag:` prefixed label from the labels so that this PR shows up in the changelog -->

[mtzhang]

Thanks for @mitchellhamilton for merging the submitted PR!

Is it possible to cut a patch release with this upgrade soon? Can I get an ETA on that? /cc @Andarist

[emmatown]

Fixed by #866

[mtzhang]

@mitchellhamilton Amazing, thank you so much! 🙏