Open lencioni opened 7 years ago
The parse error seems to happen because of object spreading. { ...foo, ...bar }
. I should be able to have a PR ready shortly.
The first set of errors seems to come from trying to follow a require from inside a node_module dependency. For jest for instance, it has a main file that does this:
module.exports = require('jest-cli');
We just assume that the require is for a local file, so we try to open the wrong path. Relevant code here: https://github.com/Galooshi/import-js/blob/9f5536319bbb5ed6d31cab74a43b05d6cc0ec9c1/lib/findExports.js#L65
I just updated to v2.1.2 and am running into some issues. I'm guessing that I have a stale cache or something. In my logs I see stuff like the following:
After removing the cache and restarting importjs, I see a bunch of the following in my logs:
The file it is failing on, looks roughly like this: