@akshaybabloo Sorry to hear that! Unfortunately this is caused by somewhat unexpected behavior in npm. The solution is to delete your node_modules folder, and run npm install --production again.
I somehow remember that this was a problem before. Maybe the official docs should be changed to tell users delete the node_modules folder in EVERY error case, not only when the npm install --production step fails. Or even better (which I think would avoid many future problems): ALWAYS delete it before doing the upgrade. This would increase upgrade times slightly, but I think it is worth it.
@crepererum normally it's fine, the only time I recall this has been a problem was in the 0.9.0-beta2 release.
In the 0.9.0-beta.2 release, it was caused by a lodash dependency issue, explained in this comment.
In the main 0.9.0 release, the same problem is occuring, except it's with knex instead of bookshelf. A maintenance release will be issued sometime soon to fix the issue.
For the record this just happened to me while going from 0.8.0 to 0.9.0, and I found this by specifically searching for the lodash and ghost.
Seems like a step too many when including a note to try deleting the node_modules directory would resolve the situation for many.
@mattlacey sorry to hear you had this problem. Where did you expect to see the note? It is included in the troubleshooting section of the upgrade guide.
You know what, I spotted that right after! I think I missed it because I'd
scrolled down to just the command list after the first upgrade round (I was
going 0.7 -> 0.8 -> 0.9 -> 0.10.1) and then forgot about that.
I guess including it twice would be silly, maybe after the last step have
something like "If you encounter an issue refer to the troubleshooting
section above"?
On 15 September 2016 at 02:12, Hannah Wolfe [email protected]
wrote:
@mattlacey https://github.com/mattlacey sorry to hear you had this
problem. Where did you expect to see the note? It is included in the troubleshooting
section of the upgrade guide
http://support.ghost.org/how-to-upgrade/#troubleshooting.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TryGhost/Ghost/issues/7158#issuecomment-247066500,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMrWxZTXur_Bsinno6JCV_L2h_wK-o8ks5qqBzkgaJpZM4JX4o5
.
This has been done 😉
Most helpful comment
@akshaybabloo Sorry to hear that! Unfortunately this is caused by somewhat unexpected behavior in npm. The solution is to delete your
node_modulesfolder, and runnpm install --productionagain.