code-423n4 / code-423n4/code423n4.com
[BUG]: build warnings due to HEIF avatar file format
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 179
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Noticed this in the build log:
12:02:46 PM: warning You can't use childImageSharp together with 0xepley.heif — use publicURL instead. The childImageSharp portion of the query in this file will return null:
/opt/build/repo/src/pages/register.tsx
Not sure how much practical impact this has but I wonder if we should convert that to a better-supported format and/or try avoid merging HEIF images in the future?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting src/pages/register.tsx and the build warning for 0xepley.heif to determine how the avatar is referenced. Done means the build no longer reports a childImageSharp warning for that image, but the issue does not specify whether to convert the asset or change the image query.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100