-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
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
Can't use .svg?include since 2.5.6 #142
Comments
Hello @esiao |
Hi! Having a similar issue, but for: Getting:
Next.js: 9.3.4 responsive-loader: 1.2.0 |
Tested - this errors are not happening in next-optimized-images 2.5.5, even with latest Next 9.3.4. I am using built-in Next CSS. |
Here are my modules versions
I tried with 2.5.7 and 2.5.6, I had to roll back to 2.5.5 where I don't have the issue. (today still) |
That did indeed help, thank you! I just published a canary version: |
Fixed the issue for me, thank you very much! |
Hi I'm sorry I didn't answer earlier I had an hectic week! It's working perfectly fine now, thank you. I'm looking forward the next release with the fix, glad I could help you debug the issue. Thank you very much. |
No worries, we all have those weeks. I'm glad to hear that everything works, thank you again! The fix is now published as a non-canary version in |
Hello,
I've came across an issue recently upgrading my depencies.
It looks like since version 2.5.6 the raw-loader isn't loaded properly and during the build I have errors of the likes of, resulting in error 500.
If I downgrade to 2.5.5 the issue is gone and I can use my svgs as expected.
const Something = require('../assets/something.svg?include')
Hope this will help people coming across this issue until it's fixed.
Thanks for your hard work.
The text was updated successfully, but these errors were encountered: