jspm-cli: Nested dependencies not getting mapped to `config.js`
ModuleA
has roughly 20 dependencies defined within the jspm
section of its package.json
. ModuleB
wants to use ModuleA
. Using jspm install ModuleA=github:timbur/ModuleA
, ModuleB
’s config.js
doesn’t get updated with the proper map
configuration so that ModuleB
’s System
will know where to find ModuleA
’s dependencies. I’ve tried everything I could think of, other than starting completely from scratch.
I also tried reproducing the issue (see timbur/systemjs-test-c
) but that one works correctly.
ModuleA
in the above description is actually loggur/web-tedit
.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 41 (15 by maintainers)
@guybedford The overrides work, but I feel like the issues I experienced could be avoided if
jspm
defaulted tonpm
if no jspm-style dependencies are found within thepackage.json
(and no registry provided of course). I think something along these lines would work:It would also avoid having to use a ton of overrides like I’m doing here: