Closed agarzola closed 8 years ago
Looks like meta isn't being defined properly, what module were you trying to fork? I can probably reproduce it.
Thanks I'll check it out!
Hrmmm, it worked for me, but I did ship some bug fixes recently, what version of forked are you using?
EDIT: Screen shot:
0.0.11
it looks like.
I just tried it on shelljs
with the same result. Something is clearly wrong on my end. I’m on node 4.2.2, if that makes a difference.
So the way it works is forked is looking for a ./package.json
file, I am able to reproduce your error by running $ fork
in a random folder that doesn't contain a package.json
file.
I wonder what that json: command not found
is all about.
hrmmm I think the crux of the error is actually the /bin/sh: json: command not found
.
Looks like it's not able to run the parsing command, which explains why meta is undefined.
I might be wrongfully assuming environment specific things, looking into it
Right. Does it make sense that package.json defines dist/main.js
instead of dist/index.js
?
Oh that's borked too, ima fix that.
Could you try running this in your console and show me what it spits out?
$ cat package.json | json repository.url
bash: json: command not found
Clearly I’m missing that.
Well, if you are then a lot of other people probably are.
I got a PR for you in a sec.
I’m getting this error after installing, navigating to a project dependency (on an unrelated project), and using
fork
:I also noticed that line #33 seems to be missing something, which may be related. I haven’t used babel yet, though, so I might just be missing something here.