Yarn install says up to date, yet can't start rails console

Question

I've been developing an app using Webpack, Vue.js and Rails. No problems for two months, but out of nowhere when I try to start rails console rails c, yarn complains that packages out of date:

error An unexpected error occurred: "Unknown language key integrityNodeDoesntMatch".
info If you think this is a bug, please open a bug report with the information provided in "/Users/maksimfedotov/vras/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/check for documentation about this command.


========================================
  Your Yarn packages are out of date!
  Please run `yarn install` to update.
========================================

Yet when I run yarn install:

yarn install v1.3.2
[1/4]   Resolving packages...
success Already up-to-date.
✨  Done in 0.71s.

I've been looking through yarn and webpacker documentation, tried various yarn cleanup commands, but no luck.

Interestingly enough, I can still run the server, its only console that complains.

Did you try deleting `yarn.lock` and running `yarn install` again? — chumakoff, Apr 02 '18 at 14:35
I haven't tried either, but this issue just went away. Not sure what happened... — Maxim Fedotov, Apr 15 '18 at 16:43
I have the same issue with running `rails c` and `rails g ...`. Deleting node_modules and yarn.lock doesn't help — ktaras, Sep 09 '18 at 08:13
Please remember to try `spring stop` as a simple fix after every configuration change and before deleting anything. — MustModify, Dec 03 '21 at 15:22

score 20 · Accepted Answer · answered Mar 17 '19 at 17:53

20

This is an old issue, which has been resolved, so I am writing down what I did in the end:

Simply deleting node_modules usually solves the issue. If you are using spring, it also can mess this up, so consider running DISABLE_SPRING=1 rails s to see if that helps

answered Mar 17 '19 at 17:53

Maxim Fedotov

1,349
1
18
38

Deleting node_modules didn't work for me, but disabling spring did. Is there a way to get spring and webpacker to play nice together? – lucas Aug 08 '19 at 15:29

score 17 · Answer 2 · answered Aug 08 '19 at 15:43

Try restarting spring by running spring stop.

This fixed the issue for me, and meant I didn't need to constantly prefix commands with the spring disable flag.

The above command stops spring: to check that it automatically restarted, run spring status.

Credit to this comment on GitHub for the solution!

score 5 · Answer 3 · answered Mar 05 '20 at 15:58

You can add in the config/environments/development.rb

this configuration setting

config.webpacker.check_yarn_integrity = false

It also it forget to check yarn integrity on every rails call, as migrations, launching consoles ..., in development environment

stevec · Answer 4 · 2021-05-01T17:34:07.330

This problem resurfaced in April 2021 due to compatibility issues between node-sass and node version 16. (I had similar problems here and provide a similar answer to that below here).

So my solution is to downgrade node until version 16 is fully compatible.

Install node 14 with nvm install 14, then set it to the global default with nvm alias default 14.

Then:

Stop your rails server if it's running
Open a fresh new terminal window (so that node --version returns 14.x (not 16)
Run spring stop
Delete yarn.lock
Remove existing node modules with rm -rf node_modules
Check that node --version returns 14. If it doesn't run nvm install 14 again.
Now reinstall modules with yarn install (if you don't have yarn for node 14, install it with npm install --global yarn)
It should succeed!
Restart your rails server, and it will work!

Other useful info:

This github issue - this comment in particular

The only thing I would add, as a possible extra, is to use a `.nvmrc` with the version added to it — BenKoshy, Jan 07 '22 at 05:10
@BenKoshy I should probably update this because I think node-sass library has been corrected since, so going to the most recent node version might work now (I’m speculating though) — stevec, Jan 07 '22 at 05:13

Feuda · Answer 5 · 2019-09-11T10:29:47.583

0

Try just yarn install then rails c again

edited Sep 11 '19 at 10:29

answered Sep 11 '19 at 10:24

Feuda

2,335
30
28

score 0 · Answer 6 · answered May 13 '20 at 21:48

If you are switching branches which change yarn.lock and just want to run a rails console without having to keep running yarn install everytime you switch, you can add this to your app/config/development.rb

config.webpacker.check_yarn_integrity = ENV['SKIP_YARN'].nil?

Then when rails complains you can simply do this

SKIP_YARN=true rails c

score 0 · Answer 7 · answered Jul 08 '20 at 01:30

0

In my case, this solve the problem.

rm -rf yarn.lock
yarn install

answered Jul 08 '20 at 01:30

Son Tr.

776
6
18

score -1 · Answer 8 · answered Apr 07 '18 at 18:02

-1

Try this: NODE_ENV=development yarn install

answered Apr 07 '18 at 18:02

Samuel Danielson

5,231
3
35
37

Yarn install says up to date, yet can't start rails console

8 Answers8