Components or presets for LCP and lazy elements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
Hey there!
I recently thought about a feature addition to the Nuxt Image that will deliver following functionality in form of additional component or a preset:
- Largest Contentful Paint element that will not be lazy loaded, will have a fetchPriority high, preload, and maybe more
- Lazy element, that will have loading lazy, fetchPriority low, etc.
This way, users would be able to just set a preset for the element that they want to be loaded first (LCP) and the ones that can be loaded after (i.e icons in the footer).
WDYT?
I am happy to contribute with this change if you think that it will make sense :)
Contributor guide
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 reviewing Nuxt Image's existing component and preset APIs to determine where LCP and lazy-loading behavior could fit. Done means the project has agreed on the component or preset scope and its expected loading, priority, and preload behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt
- Domain
- frontend, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100