Getting err about lodash about yarsk

[bradleyboy]

@winkler1 That's odd. I just did a fresh clone and didn't get that. Maybe something went wrong during npm install? Can you try deleting node_modules and trying npm install again?

[winkler1]

Did some testing--
New machine: Works just fine. webpack-dev-server -v -bash: webpack-dev-server: command not found

Original/bad machine: rm'd node_modules, still fails. Re-cloned, still fails. webpack-dev-server is 1.7.3

The difference could be the fact that the package.json is using the global webpack/dev-server, not within node_modules?

[bradleyboy]

Good point. Just pushed a fix that uses the full path to webpack and the dev-server, see if that fixes it.

[winkler1]

Unfortunately not on the bad machine. Will try to run some experiments this weekend. I'm thinking to save off global NPM state, see if that makes a difference.
Really like this starter kit btw... I'll add in react-router and probably flummox on real projects, but you're wise to minimize the surface area :)

[winkler1]

npm cache clean did the trick, closing.