Subsequent requires done properly
Open
bug
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Subsequent requires done inside of an oldRequire (original) should be done with oldRequire and not pass through mocka framework
Contributor guide
Research direction
Start by locating oldRequire and the handling of subsequent requires. Trace a subsequent require made inside an original oldRequire, then verify the stated boundary: it should use oldRequire rather than pass through the mocka framework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100