I would call this normal behavior because you should only be importing stuff from CDNs and from within the project folder. It does make the situation a little ugly for monorepos though, monorepos with deno is something that is still being figured out though anyways.

You only use "../" or "./" relative paths when the file exists locally in your machine. If it doesn't then you should be using an URL to import from wherever you have it

hum my other projects inside the monorepo work well (install, bundle...).
I don't understand why a TS file inside my project works and just above is KO?

With a symlink of the external project inside root of aleph project, it is ok.

This might be due to the fact that alephjs movies files around before executing them. I know this isn't an import but this is how I access files.

import * as path from "https://deno.land/[email protected]/path/mod.ts";

const dir = path.fromFileUrl(import.meta.url);
const projectDir = path.resolve(dir, "../../../../"); // The files are located in the same directory (api), but in order to work, you need to move up 4 directories for the project root directory.
const schemaFilePath = path.resolve(projectDir, "api/schema.gql");

Deno.readTextFileSync(schemaFilePath);

@RoXuS Can you please show your project structure? I feel like I am giving advise without actually knowing what I'm dealing with

@Soremwar off course.

My structure:

My components/runners.tsx try to access to dt-gitlab-wrapper/index.ts and it doesn't work (with a symlink it is ok).

@FallingSnow it seems hard to do that with a file import like import a from "../../dt-gitlab-wrapper/index.ts"; no?

Yeah. I don't know if deno supports require, I've never tried but that could be a possible solution.

i seems the git-wrapper is out of your aleph app scope that alephjs can't handle it, I will fix this, thanks!

please use synlimk as workaround currently

works as expected on 1.8.0, THX!