Method of disabling multiple instances warning
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36.1k
- Forks
- 1.1k
- Avg merge
- 9h 18m
- Merged PRs (30d)
- 195
Description
I'm getting the warning:
You appear to have multiple instances of Solid. This can lead to unexpected behavior.
I don't think there's actually any issue in my case. The two instances/components don't share any common root and I don't want them to interact in any way. Also, one of the instances is present only in development, so I'm not worried about extra bytes being shipped to production because of an extra copy.
I would love if there were some way to disable this warning since I don't think it's actually a problem in my case.
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 locating the code that emits the “multiple instances of Solid” warning; the issue does not name a file, test, or entry point. Determine how an opt-out would apply when instances have separate roots and when one exists only in development. Done means the warning can be disabled for this use case without affecting other instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100