Skip to content
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

Using next/image has introduced a problem #177

Open
jameslieu opened this issue Aug 15, 2022 · 0 comments
Open

Using next/image has introduced a problem #177

jameslieu opened this issue Aug 15, 2022 · 0 comments

Comments

@jameslieu
Copy link

Describe the bug

1st Issue

The first issue is the Next/Image component requires the width and height properties.
Screenshot 2022-08-15 214839

2nd Issue

When clicking into a profile, Next/Image component requires that you define the hostname of a given src in the images.domains config in next.config.js, the problem with this is that if a user wants to use an image from an alternate source like their personal website, or twitter or FB, you would need to add that hostname into the config, so there is a huge restriction placed when using this component. https://nextjs.org/docs/messages/next-image-unconfigured-host

Screenshot 2022-08-15 221205
https://nextjs.org/docs/messages/next-image-unconfigured-host

To Reproduce
Steps to reproduce the behavior:

  1. Go to the landing page
  2. Click on a profile

Expected behavior
The page should load.

Proposed solution

Revert the element back to img, there is a eslint warning which states to either use the next/image component or to use in conjunction with element:

https://nextjs.org/docs/messages/no-img-element

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

No branches or pull requests

1 participant