Repository navigation
Return errors when importing unsupported content types #87
Description
Currently if you import a Notion page that has either a database or a checkbox, the library appears to simply not load — ideally the library should return an error and explain what the unsupported content is, eg:
"This Notion document includes a Database which we cannot import, please remove the Database to render this page"
Activity
vczb commentedon Sep 20, 2021
Hi, would you like the message "This Notion document includes a Database which we cannot import, please remove the Database to render this page" on the screen? or as an alert ?
I see a log similar at you like to say on this file (src/block.tsx), line 490
plc commentedon Oct 6, 2021
Yeah exactly - so sorry for the slow reply.
webbdays commentedon Jan 7, 2023
I would like to work on this.
JaneX8 commentedon Nov 29, 2023
I don't know why it's not mentioned here, but there is a bounty on this issue of USD 150,-.
https://gitpay.me/#/task/534/return-errors-when-importing-unsupported-content-types
vibhuti019 commentedon Apr 5, 2024
@webbdays Are you working on this issue ?
webbdays commentedon Apr 5, 2024
I would like to.
But no one responded.
Will look into this issue this weekend.
webbdays commentedon Apr 6, 2024
dropping.
pnogemane commentedon Nov 10, 2024
Is this issue still available to pick up?
gscofano commentedon Jun 22, 2025
@plc I would like to work on this. Is this feature still needed?
kallal79 commentedon Oct 22, 2025
Hi @plc, Please assign me #87. I’ll implement clear error handling for unsupported Notion content types. Ready to start.
feat: Add user-friendly error handling for unsupported block types
hieu-lee commentedon May 11, 2026
Opened PR #130 with a focused implementation for this: #130
It renders clear unsupported-block errors by default, preserves the previous empty-placeholder behavior behind
showUnsupportedBlockErrors={false}, supports a customrenderUnsupportedBlockfallback, and keeps existingcustomBlockComponentsbehavior intact.Verified with
npm test -- --runInBand,npm run build,npm run lint, andgit diff --check.