Skip to content

Conversation

@artfuldodger
Copy link
Contributor

Ensure people realize when they've configured sprockets to not use any resolvers.

Motivation: I was upgrading a legacy app and the staging configuration resulted in an empty resolve_with array (much to my dismay), and it took some digging to figure out the source of the "is not present in the asset pipeline" error. I hope this can save someone some time in the future.

Ensure people realize when they've configured sprockets to not
use any resolvers.
@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @schneems (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants