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

Getting err about lodash #4

Closed
winkler1 opened this Issue Mar 19, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@winkler1

winkler1 commented Mar 19, 2015

Trying it out...get this after npm install. Installing lodash does not fix it-

$ npm run serve

> bradleyboy-react-starter@1.0.0 serve /Users/Jeff/repos/ghtemp
> webpack-dev-server --config conf/webpack.config.js --hot --progress --colors --inline --content-base ./build

http://localhost:8080/
webpack result is served from /
content is served from /Users/Jeff/repos/ghtemp/build
-25% 1/4 build modules
/Users/Jeff/repos/ghtemp/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:204
                    throw e;
                          ^
Error: Cannot find module 'lodash/lang/isFunction'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/Jeff/repos/ghtemp/node_modules/babel-core/lib/babel/api/node.js:13:34)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
@bradleyboy

This comment has been minimized.

Show comment
Hide comment
@bradleyboy

bradleyboy Mar 19, 2015

Owner

@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?

Owner

bradleyboy commented Mar 19, 2015

@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

This comment has been minimized.

Show comment
Hide comment
@winkler1

winkler1 Mar 19, 2015

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?

winkler1 commented Mar 19, 2015

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

This comment has been minimized.

Show comment
Hide comment
@bradleyboy

bradleyboy Mar 19, 2015

Owner

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

Owner

bradleyboy commented Mar 19, 2015

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

@winkler1

This comment has been minimized.

Show comment
Hide comment
@winkler1

winkler1 Mar 20, 2015

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 commented Mar 20, 2015

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

This comment has been minimized.

Show comment
Hide comment
@winkler1

winkler1 Mar 21, 2015

npm cache clean did the trick, closing.

winkler1 commented Mar 21, 2015

npm cache clean did the trick, closing.

@winkler1 winkler1 closed this Mar 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment