-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version issues with node and grunt #298
Comments
Thank you for the detailed write up!! This is definitely something that should be fixed -- setup should be as painless as possible. I ran
I think that most of these should be pretty painless / safe to update, I'll give it a go. |
Godspeed and many thanks!! :D I'm not sure about any of the others, but I know that that lodash 4.x definitely introduces breaking changes. Maybe try updating everything but lodash first? |
This isn't really an issue with this project per se, but I wanted to document my experience in case it helps others.
I cloned the repo and ran
npm install
. I didn't havegrunt
already, so I installed it globally,npm install -g grunt
. Then I went to rungrunt dev
to build the project and I get an error -Boooo. So I googled and this error is documented here and here. I followed the suggestion from that first link and updated all my dependencies. Now
grunt
works like a charm, yay!But I start dev'ing and I run into a bunch of issues with the development build of the extension... (you can see where this is going...). After some debugging, I realize that the problem (or one of them, anyway), is that I updated to a backwards-compatibly breaking version of lodash and scope binding was all screwed up.
At that point, I realized how foolish it was to just update all the project dependencies and expect that nothing would break. 🙃 🔫 So I wiped
node_modules/
and started over. Since many of the dependency versions are quite old, I figured the problem was with the version of node that I was using (v7.2.1), so I installednvm
and versionv6.9.0
and viola, problem solved! I could now use grunt.So yeah, like I said, not a problem with this project per se, but a headache for me when I thought what I wanted to do would be super simple. Perhaps the project could include an
.nvmrc
to make it explicit that node 7 isn't going to work out? Either way, I hope documenting this here saves other folks some time. ❤️The text was updated successfully, but these errors were encountered: