-
-
Notifications
You must be signed in to change notification settings - Fork 29
Next/image with imgix loader #67
Comments
Thanks for reporting the issue! This is actually a bug. I'm consistently humbled by how well users can find blind spots in my code lol. The issue is that I don't load the image config like nextjs does. Right now I ignore it. I'll get to work on this soon. |
Thanks for fast response! Also want to take the opportunity to say thank you for running this package. Just started to use it but really saves a lot of the hassle to make Next work with Storybook. |
Thanks a bunch! That means a lot :) I'm glad it's working out for you. |
This seems to be solved also by solving #70. So check there for updates for now. |
This issue has been automatically marked stale because it it received no activity for 60 days. If you wish to keep this open, please leave a comment. Thanks. |
Go away |
This issue has been automatically marked stale because it it received no activity for 60 days. If you wish to keep this open, please leave a comment. Thanks. |
This issue has been automatically closed because it received no activity for 60 days. If you think this was closed by accident, please leave a comment. Thanks. |
I have created this discussion to centralize supporting these nextjs props #119 |
Describe the bug
Does not add absolute path to the imgix server for the img src.
Your minimal, reproducible example
Sorry no repo...
Steps to reproduce
Use
next/image
component in a story with the following configuration:next.config
Component with
next/image
Expected behavior
When running Next (
yarn dev
) the img src will automatically be set tohttps://my-account.imgix.net/7f552320-6810-5a2d-8a47-521b22068ae5
.When running Storybook the img src will only be
7f552320-6810-5a2d-8a47-521b22068ae5
right now. This results in a load to localhost and a 404 response.How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
macOS
storybook-addon-next version
v1.6.2
Additional context
No response
The text was updated successfully, but these errors were encountered: