Kedi Comments

Kedi

Posts Comments

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

I was also looking for a solution hahaha

8 replies

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

thanks

8 replies

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

@Rob S Deno workspaces supports the same behaviour as Pnpm workspaces:

  "name": "@repo/core",
  "exports": {
    "./utils": "./utils/mod.ts",
    "./services": "./services/services.ts",
    "./errors": "./services/errors.ts",
    "./types": "./types/mod.ts",
  }

  "name": "@repo/core",
  "exports": {
    "./utils": "./utils/mod.ts",
    "./services": "./services/services.ts",
    "./errors": "./services/errors.ts",
    "./types": "./types/mod.ts",
  }

the confusion is just due to lacking of documentation

8 replies

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

consider mentioning ur problem also there

8 replies

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

I opened an issue https://github.com/denoland/deno/issues/28019

8 replies

DDeno

•Created by Rob S on 2/1/2025 in #help

Workspace documentation lacks explanation of `exports` member in deno.json

It is really frustrating, I think u should open an issue, the only solution I found, was to export just one file as the docu says (one file per workspace), which is very limiting unlike for example pnpm workspaces

8 replies