You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rails-ujs appears in the manifest, but so do other things that requirejs, so, requirejs should come before application.
Trying to put require after application might work, but would involve taking other defines out of assets.
I'm not sure what the current thinking is. Looked at requirejs-rails, but open issue there: jwhitley/requirejs-rails#268
I think maybe asset pipeline isn't compatible with requirejs, but then why attempt to support amd defines in rails-ujs? Is there a requirejs config I'm missing?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 6-0-stable branch or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.
Steps to reproduce
Expected behavior
page should load
Actual behavior
Console error in Firefox dev tools:
System configuration
Rails version: 5.2.4.3
Ruby version: 2.6.6
Source causing the issue
from the gems directory
These are all anonymous defines. See https://requirejs.org/docs/errors.html#mismatch
Attempted Workaround
rails-ujs appears in the manifest, but so do other things that requirejs, so, requirejs should come before application.
Trying to put require after application might work, but would involve taking other defines out of assets.
I'm not sure what the current thinking is. Looked at requirejs-rails, but open issue there: jwhitley/requirejs-rails#268
I think maybe asset pipeline isn't compatible with requirejs, but then why attempt to support amd defines in rails-ujs? Is there a requirejs config I'm missing?
The text was updated successfully, but these errors were encountered: