NotionX / NotionX/react-notion-x
Can split previewImages and nextImage into two separate functions?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
Description
Due to images on the domain notion.so cannot be accessed in some regions, I'm seeking a way to add an integrated image proxy for my site to bypass the restrictions.
The images in NotionRenderer component will not be replaced by Next Image unless the previewImages fuction got implemented as well.
As I just want to add the image proxy, is it there any way to use the standalone nextImage to control the image wrapper in NotionRenderer?
Notion Test Page ID
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
Locate the NotionRenderer component and the previewImages and nextImage implementations; read how image rendering is wired together. Done means the image proxy use case can control the NotionRenderer image wrapper independently from the standalone nextImage behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100