MeepM
Deno•16mo ago•
9 replies
Meep

Dependency tree not resolving properly for deno modules in local filesystem.

Background:
I'm working on an application with many custom utilities as dependencies. I have these utilities divided out into smaller 
deno.json
 packages for better organization. All of these utility packages are on my local filesystem, and since I'm still working on development and planning still I'm unlikely to publish them at the moment. Some of these utilities depend on eachother and form a tree of package dependencies; all on my local filesystem. Some of the utilities are shared between multiple projects and are kept in a separate generic libs folder on my filesystem.

Issue
For some reason I'm getting an error when trying to test my application with 
deno run
: 
C:\Users\super\meep-tech\projects\Kept\deno\apps\kms> deno task run:dev

Relative import path "@meep/args" not prefixed with / or ./ or ../ and not in import map from "file:///C:/Users/super/meep-tech/libs/ts/deno/tsx/src/tsx.ts"
    at file:///C:/Users/super/meep-tech/libs/ts/deno/tsx/src/tsx.ts:3:18


Given these imports in the 
deno.json
 files for each package i'd expect it to work as expected:
- for @meep/kms (the app which was run)
  "imports": {
    "@meep/tsx": "../../../../../libs/ts/deno/tsx/src/mod.ts"
  },

- for @meep/tsx
  "imports": {
    "@meep/args": "../args/src/mod.ts",
  },


Any advice on what I'm doing wrong?
Was this page helpful?