It looks like you have a lot of cleaning up. Is this your first Rails app? If so, I'm curious why you have so many JS files. I would shorten the list to a few, fix the problems that remain, and slowly begin to add things and fix problems when you go. That would be my overall strategy. For each mistake, slowly and twice check that you really understand the reason before you swear here and there, hoping for a fix.
Here are some tips for specific errors that I see:
This line will include all .js files in app/assets/javascripts :
The problem is that you have already turned them on one by one. Therefore, they are turned on twice. That's why you get warnings like 'findGoodContent' has already been declared . I know it’s nice to use require_tree (although I don’t like it), so if you want to keep this, consider moving all third-party JS files from app/assets/javascripts and to vendor/assets/javascripts . You can still require them in your application.js , but they will not be repeated using require_tree .
404 errors for things like grayscale.svg and flaticon.woff , as well as other image / font resources - this is because you do not have these files in app/assets (or vendor/assets ). Or if you do, you need to make sure your JS / CSS files and view files refer to them using <%= asset_path "grayscale.svg" %> , so that when Rails manages its path, you still load them from the right place. Read about image_url and friends and make sure you understand how they work. By default, Asset Pipeline uses unused names in development and distorted names in production, so everything can work until you hit everything alive!
In addition, if you add <%= foo %> tags to a CSS or JS file, you need to add the .erb extension to this file so that Rails knows how to handle these tags. This is why you get a 404 error trying to download this:
http://localhost:3000/assets/%3C%=%20asset_path('random.jpg')%20%%3E
In one of your files, possibly in a CSS file, you are doing something like this:
background-image: url("<%= asset_path('random.jpg') %>");
But the file requires the extension .erb : blah.css.erb or blah.scss.erb or something else.
Errors like $ is not a function mean that these files are jQuery dependent, but the jQuery $ object is undefined. If you use noConflict , as someone suggested in the comments, you should stop because you want $ be a jQuery object.
Good luck If you feel depressed, I would really start by cutting out as many JS require lines as possible, as well as fixing errors one at a time.
In addition, I would reorder the require strings so that the dependencies are at the top (like jquery), and everything that relies on them is lower.
Oh, one more thing, actually not a mistake: I would not put mini files (for example, hammer.min.js ) in your repository. An asset provider knows how to minimize. So check the non-urgent version so that if you need to read the source code, you can.