We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following is error info when run rack test.
Sprockets::FileOutsidePaths: /gems/opal-1.3.2/opal/opal.rb is no longer under a load path: /assets/css, /assets/js, /vendor/assets/materialize-src, /opal-1.3.2/opal, /opal-1.3.2/stdlib, /opal-1.3.2/lib, /ast-2.4.2/lib, /ast-2.4.2/lib, /parser-3.0.3.1/lib, /snabberb-1.5.4/opal, /opal-browser-0.3.1/opal, /paggio-0.3.0/lib /sprockets-4.0.2/lib/sprockets/loader.rb:156:in load_from_unloaded' /sprockets-4.0.2/lib/sprockets/loader.rb:59:in block in load' /sprockets-4.0.2/lib/sprockets/loader.rb:337:in fetch_asset_from_dependency_cache' /sprockets-4.0.2/lib/sprockets/loader.rb:43:in load' /sprockets-4.0.2/lib/sprockets/cached_environment.rb:44:in `load'
It works when i use opal 1.3.1 before, after update to 1.3.2, those error is happen.
Thank you.
@hmdne said:
A known issue, but it's rather an opal-sprockets issue.
You need to erase your cache when gem paths change.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Following is error info when run rack test.
It works when i use opal 1.3.1 before, after update to 1.3.2, those error is happen.
Thank you.
@hmdne said:
A known issue, but it's rather an opal-sprockets issue.
You need to erase your cache when gem paths change.
The text was updated successfully, but these errors were encountered: