`--optimize` → `Browser.Dom.NotFound` becomes undefined
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 5
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 1
Description
Contributor guide
No contributing guide indexed for this repository
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
The issue body only links to https://github.com/elm/browser/issues/63; no source files, tests, or entry points are named. Start by reading that linked report and tracing the --optimize build path for Browser.Dom.NotFound. Done means Browser.Dom.NotFound is defined rather than undefined in optimized builds, with a regression test if the project identifies a suitable test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100