[TIMOB-6012] Android: Better error message for wrong module path
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-09T16:55:45.000+0000 |
| Affected Version/s | Release 1.7.5 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | n/a |
| Reporter | Kevin Whinnery |
| Assignee | Eric Merriman |
| Created | 2011-11-04T21:23:41.000+0000 |
| Updated | 2017-06-09T16:55:45.000+0000 |
Description
When I fat fingered the path to a module in my project, the error message I got was misleading: "NOT_FOUND is not defined at line 1". When the module path is incorrect, and error message indicating this would be helpful for debugging. To reproduce, attempt to require a module using the wrong path, as in:
exports.foo = 'bar';
Usage:
var mod = require('somethingwrong/mod.js');
Closing ticket due to time passed, any problems please open a new ticket.