When NPM Installation is messed up after updating new node/npm

You may lose your authority to amend your node-modules -especially, if you see ‘lock/unlock’ words on logs.

This solution works for me.

http://stackoverflow.com/questions/22152162/npm-cannot-install-dependencies-attempt-to-unlock-something-which-hasnt-been

Enjoy!

Advertisements

Update NPM/NODE all the time!

Grrr..

I was working on React study with using gulp. I usually act on yeoman/grunt but I guess gulp is rising and need to use it.

So far it was totally okay to use gulp and serving ,at some point, on gulp brings whole knocked out.

The problem was solved next day with updating all packages globally.

Remember, When you use evolving platform/library, always do update npm and node.

Here is useful stackoverflow link.

http://stackoverflow.com/questions/8191459/how-to-update-node-js

Enjoy!

Good Git links

Even though I have kept using Git, sometimes it confuses me on which command I should put. I, however, don’t want to bother myself to look into a few hundreds pages book to just a line.

For some who has same issues as me,

Here are useful links

  1. Atlassian simple work flow

http://blogs.atlassian.com/2014/01/simple-git-workflow-simple/

  1. Git the simple guide

http://rogerdudler.github.io/git-guide/

Enjoy!