Closed
Bug 1107650
Opened 10 years ago
Closed 8 years ago
toolkit/loader must lookup node_modules relative to reqiurer first before jumping to a rootURI
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: irakli, Unassigned)
References
Details
No description provided.
|
||
Comment 1•10 years ago
|
||
This is caused when instrumenting your own loader (unlikely to run into in traditional jpm usage), and requiring files outside of the rootURI children path. Example:
rootURI: /Projects/my-projects/project
And scaffolding a require for something out of that path like:
/Projects/other-project/module
That require, with `/Projects/other-project/module` as the requirer, will attempt to look up node_modules within `/Projects/my-projects/project` rather than recursively going up looking for node_modules, up until the rootURI.
A possible issue with this is since the look up is not under rootURI, this could recursively go up to `/` looking for the node module.
|
||
Updated•10 years ago
|
Blocks: jpm, native-jetpack
|
|
||
Updated•10 years ago
|
Blocks: toolkit/loader
|
|
||
Updated•10 years ago
|
Priority: -- → P2
|
||
Comment 2•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•