Can't use relative imports above jsr.json location

[alexgleason]

I am doing this in mod.ts:

import { NostrEvent } from '../interfaces/NostrEvent.ts';

It fails:

I am importing ../interfaces/NostrEvent.ts while having ./jsr.json. So the file I'm importing is above jsr.json

If I move jsr.json up a directory, it works. But I don't want to do that, because I'm trying to manage multiple packages in one repository, with some code copied between them. Kind of like a monorepo.

deno publish --dry-run doesn't complain. But the package is refused by JSR.

The package is: https://jsr.io/@nostrify/ndk (Which I finally got to work by temporarily moving jsr.json up one directory)

[marvinhagemeister]

FYI: Workspace support in Deno isn't ready yet. Support for workspaces is being tracked here denoland/deno#22942

[alexgleason]

Good to know. But this problem would occur even with ~/Projects/myproj/mod.ts importing ../otherproj/b.ts

Importing local code from outside of the JSR working directory should work, right?

[marvinhagemeister]

Right now the assumption is that the packages jsr.json/deno.json is at the root of the package. Once support for workspaces land it will be possible to reference packages in other folders, but not importing files from above the package folder. It's very unlikely that we'll ever add support for that as it introduces significant complexity and edge cases during the publish process.

We haven't decided on that in the team yet, but my feeling is that we'd rather spent time working on other JSR stuff in the coming months. I wouldn't plan my code around this being supported anytime soon (if at all).

[alexgleason]

Thank you for clarifying @marvinhagemeister

In that case I'll close this in favor of denoland/deno#22942