Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Custom import warning

Open
#207 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

No file, test, or entry point is named. Start by locating the editor's handling of import errors; done means import attempts display clearer guidance about providing components in the react-live scope and include a project-specific tutorial link.

Written by the indexing model from the issue text.

Description

enhancement

Hi,

I know it's not possible to use imports in the editor. Was wondering if it's possible to customize the error message in case the user tries to import something.

image

Instead of this error message, I'd like an error message explaining how the user should provide the components in react-live scope, with a link to a tutorial on how to do so in the context of my project.

I think many people try to import things in react-live, and it fails with this unfriendly message. It happened to me and I've seen some issues about that already.

Does it make sense?

Dominant language
TypeScript
Stars
4.6k
Forks
260
Avg merge
6d 18h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FormidableLabs/react-live

All issues in FormidableLabs/react-live

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.