sprockets | Rack-based asset packaging system | Application Framework library

ModuleNotFoundError: Module not found: Error: Can't resolve '@popperjs/core' suggests that you need to install @popperjs/core.

Whenever you run a Rails command, it will potentially set up a bunch of classes before doing the actual work, and unlike many other languages, in Ruby this setup is done by actual Ruby code (this is how DSLs work), and any broken code that runs during that time will prevent any commands from running.

It won't run any instance methods, but any broken class-level code will cause issues.

So the migration thing is just a red herring, presumably all your Rails commands are broken.

According to your stacktrace, app/models/user.rb:8 (which you haven't provided), is getting run during initialisation. Models getting loaded during initialisation is quite common, but in this case that code is breaking.

Looking at the ActiveRecord source code (with less -N `bundle show activerecord`/lib/active_record/persistence.rb and looking at line 138), you seem to be calling the destroy class method (e.g. User.destroy(1)) but without parameters, like you do with the destroy instance method (e.g. User.find(1).destroy). So you should make sure you understand the difference between these two.

I'm not sure why you would be calling User.destroy outside of an instance method, but not having the relevant user model code I cannot say. Is there just a stray "destroy" by itself there?

This is a known issue with the current version of administrate-field-nested_has_many, and there's a PR currently in the queue that should solve it (see https://github.com/nickcharlton/administrate-field-nested_has_many/pull/45).

For the time being, you should be able to work around the issue by adding the following lines to your manifest.js:

The sass-rails gem was actually depreachiated a long time ago. Its a rails (sprockets) wrapper for the venerable Ruby SASS compiler which is extremely slow. It was replaced eons ago by sassc-rails which used libsass (which is writen in C) until that was also axed. You don't need or want it in your bundle.

The primary implementation of SASS is now Dart Sass. You can install it through Node.js, Homebrew, Chocolate, Scout-App etc. You integrate it with webpack through the Sass-loader package.

It supports features like the new module system @use that replaces the problematic @include that are starting to show up in cutting edge frameworks and will be blazingly fast compared to the old Ruby compiler.

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

It appears this error was caused by having my bashrc set RUBYOPT=rubygems which seemed to cause weird mixing of code issues. Dunno how or why but that seemed to be the issue so maybe this will help someone else avoid lots of pain and suffering trying to chase it down themselves.

It seems to be a recent bug as reported in issue 133 and 197

One solution is to use an older sassc version. In particular, I've tried:

From your ruby -v, I see that you are in an Intel x86 Mac, but the gem that your trying to build (nokogiri-1.11.3-arm64-darwin) is for new Mac ARM M1 chips. If this is the cause, it means your are using precompiled gems.

Try uninstalling the gem, specify that you don't want to use precompiled gems, and reinstall.

try running