complete example : yarn start : unknown plugin "lodash"

[theophanemayaud]

Do you want to request a feature or report a bug?
BUG

What is the current behavior?
example complete fails to run/build

What is the expected behavior?
Run/build example complete

Which versions of dependencies, and which browser are affected by this issue? Did this work in previous versions or setups?
I have yarn 1.4.0, did not change any of the package.json, but got, when running yarn :

Please choose a version of "react-redux-firebase" from this list: (Use arrow k
eys)
❯ 2.1.1 
  2.1.0 
  2.0.7-alpha 
  2.0.6 
  2.0.5 
  2.0.4 
  2.0.3 

I chose the latest 2.1.1
Then

warning codecov > request > node-uuid@1.4.8: Use uuid module instead
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "firebase > @firebase/firestore@0.4.1" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/functions@0.1.1" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/database@0.2.2" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/storage@0.1.9" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/messaging@0.2.4" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/functions > @firebase/messaging-types@0.1.3" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/firestore > @firebase/firestore-types@0.3.0" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/database > @firebase/database-types@0.2.1" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/auth > @firebase/auth-types@0.2.1" has unmet peer dependency "@firebase/app-types@0.x".
warning "firebase > @firebase/storage > @firebase/storage-types@0.1.3" has unmet peer dependency "@firebase/app-types@0.x".

And then when running yarn start :

Steps to reproduce and if possible a minimal demo of the problem via codesandbox or similar.

[theophanemayaud]

I tried the fix proposed there but only got more problems...

[prescottprue]

@CoVoCre It seems to be because it is defaulting to the root .babelrc instead of using the babel settings in the webpack.config.js. Not sure why this is happening in your environment, but I will look into a way to prevent this from happening.

[prescottprue]

The options in babel-loader include babelrc: false to prevent fallingback to babelrc. Still not sure why I am not able to repro, but it should fix it.

[prescottprue]

Just merged that babelrc: false change along with a few other small things.

Like I said, I wasn't able to repro, so not positive of if it will fix it on your system.

Let me know if things are still not working for you and we can reopen. Thanks for reporting!