You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because it's used inside a Nightmare action, fs-extra has to be resolvable from within nightmare, which means in npm 2 it gets very messy. The following is ok:
Because it's used inside a Nightmare action,
fs-extra
has to be resolvable from withinnightmare
, which means in npm 2 it gets very messy. The following is ok:This is not ok and results in MODULE_NOT_FOUND:
Yet this is ok:
I'm not sure where things stand with npm v3 but I don't think
devDependencies
is the correct place forfs-extra
in any case.I'm honestly unsure where this should be fixed (in
nightmare
?) but it seems like the simplest workaround is to not usefs-extra
inside of an action.(Can we use fs-extra
move()
into the destination directory in the parent process rather than the child runner?)The text was updated successfully, but these errors were encountered: