Unmet peer dependencies

[DaniG2k]

Hello,

Every time I run yarn install on my Rails project I'm seeing warning messages like:

warning " > @rails/webpacker@3.0.2" has unmet peer dependency "coffeescript@>= 1.12.7 || >= 2.x".
warning "@rails/webpacker > coffee-loader@0.8.0" has unmet peer dependency "coffeescript@>= 1.8.x".
warning "@rails/webpacker > postcss-cssnext@3.0.2" has unmet peer dependency "caniuse-lite@^1.0.30000697".
warning " > vue-loader@13.5.0" has unmet peer dependency "css-loader@*".
warning " > webpack-dev-server@2.9.7" has unmet peer dependency "webpack@^2.2.0 || ^3.0.0".
warning "webpack-dev-server > webpack-dev-middleware@1.12.2" has unmet peer dependency "webpack@^1.0.0 || ^2.0.0 || ^3.0.0".

My packages.json file looks like this:

{
  "license": "UNLICENSED",
  "dependencies": {
    "@rails/webpacker": "^3.0.1",
    "vue": "^2.4.3",
    "vue-loader": "^13.0.4",
    "vue-resource": "^1.3.4",
    "vue-template-compiler": "^2.4.3",
    "vue2-dropzone": "^3.0.0",
    "vuelidate": "^0.6.1"
  },
  "devDependencies": {
    "webpack-dev-server": "^2.8.1"
  },
  "version": "1.3.2"
}

I am using node 8.9.2:

→ which node
/Users/me/.nvm/versions/node/v8.9.2/bin/node

Am I doing something incorrectly?

Thanks!

[aditya-vector]

Did you try yarn upgrade and see if it works fine? Also, I am not sure how recommended it is, but try getting rid of yarn.lock file (which helps lock your packages and dependencies) and see if it helps.

[gauravtiwari]

Please upgrade to latest version of webpacker: yarn upgrade @rails/webpacker.

[serixscorpio]

@gauravtiwari Sorry to add to this closed ticket. I'm encountering similar unmet peer dependencies even after having upgraded to latest version of webpacker 3.1.1 (using yarn upgrade @rails/webpacker). Then I tried a fresh install and came across the same unmet peer dependencies warnings.

Repro steps:

1. rails new demo
2. add webpacker 3.1.1 to Gemfile, and bundle
3. rake webpacker:install
   Warning messages:

warning "@rails/webpacker > postcss-cssnext@3.0.2" has unmet peer dependency "caniuse-lite@^1.0.30000697".
warning "webpack-dev-server > webpack-dev-middleware@1.12.2" has unmet peer dependency "webpack@^1.0.0 || ^2.0.0 || ^3.0.0".
warning " > webpack-dev-server@2.9.7" has unmet peer dependency "webpack@^2.2.0 || ^3.0.0".

resulting package.json:

{
  "dependencies": {
    "@rails/webpacker": "^3.1.1",
    "coffeescript": "1.12.7"
  },
  "devDependencies": {
    "webpack-dev-server": "^2.9.7"
  }
}

I use yarn version 1.3.2.

[gauravtiwari]

@serixscorpio No problem :)

Those warnings are harmless (apart from generating noise) but if you are concerned you can use versions of webpack-dev-server per warnings since it's a peer dependency.

[jaredbeck]

Please upgrade to latest version of webpacker: yarn upgrade @rails/webpacker.

So, bundle exec rails webpacker:install installs an old version? Should we add yarn upgrade to the instructions in the readme? Or should we fix webpacker:install?

[jrochkind]

Those warnings are harmless (apart from generating noise) but if you are concerned you can use versions of webpack-dev-server per warnings since it's a peer dependency.

I am very new to fancy modern style of JS and webpack in general. I do not understand how to follow those instructions to "use versions of webpack-dev-server per warnings." Can you add an example for those who find themselves here? Thanks!

[gauravtiwari]

I am not sure if this is an issue with the latest RC (version 4).