Jad
Jad•6d ago

deno.json glob exports

I am using a monorepo with multiple projects. I would like to use specific files from package @namespace/toolbox in package @namespace/project. In package toolbox, I have the following deno.jsonc: 
{
  "name": "@namespace/toolbox",
  "version": "0.1.0",
  "description": "A collection of tools for our projects",
  "exports": {
    ".": "./mod.ts",
    "./vendor/*": "./vendor/*",
  }
}
{
  "name": "@namespace/toolbox",
  "version": "0.1.0",
  "description": "A collection of tools for our projects",
  "exports": {
    ".": "./mod.ts",
    "./vendor/*": "./vendor/*",
  }
}
In project project, I can do: 
import { thing } from '@namespace/toolbox'
import { thing } from '@namespace/toolbox'
No problem. but I am unable to do: 
import { thing } from '@namespace/toolbox/vendor/thing.ts'
import { thing } from '@namespace/toolbox/vendor/thing.ts'
I can make it work with the following jsonc: 
{
  // ...
  "exports": {
    ".": "./mod.ts",
    "./vendor/thing.ts": "./vendor/thing.ts",
  }
}
{
  // ...
  "exports": {
    ".": "./mod.ts",
    "./vendor/thing.ts": "./vendor/thing.ts",
  }
}
But this is a project with many files, and I would rather not list them individually. What am I doing wrong? PS: I wasn't sure which tag matches better with my question; I didn't find "publishing". There's an "npm publishing" tag, but that doesn't fit my case, I am not publishing any of these packages, they're only for internal usage
2 Replies
Jad
JadOP•6d ago
Found it after posting (I'd been looking for a while): https://github.com/denoland/deno/issues/26693
GitHub
Deno fails when a package in a monorepo uses a ./* export · Issu...
Deno version $ deno --version deno 2.0.4 (stable, release, x86_64-unknown-linux-gnu) v8 12.9.202.13-rusty typescript 5.6.2 To demonstrate the issue I created the following mono-repo $ tree . ├── a ...
Jad
JadOP•6d ago
It's not supported apparently I then have a subsequent question: if I import everything from a mod.ts that exports all the packages in my repo, does tree shaking still work? My concern is bundling my entire toolbox (hundred of files) in client-side code when I only need some internal functions Well, no, no need to query sub-items specifically, tree-shaking is smart enough to tree-shake unused things. Demonstration: 
// a.ts
export const toolA1 = () => {
    console.log("Tool 1");
};

export const toolA2 = () => {
    console.log("Tool A 2");
};

export const unusedFunctionA = () => {
    console.log("This will be tree-shaken A");
};
// a.ts
export const toolA1 = () => {
    console.log("Tool 1");
};

export const toolA2 = () => {
    console.log("Tool A 2");
};

export const unusedFunctionA = () => {
    console.log("This will be tree-shaken A");
};
// b.ts
export const toolB1 = () => {
    console.log("Tool B 1");
};
// b.ts
export const toolB1 = () => {
    console.log("Tool B 1");
};
// mod.ts
export * from "./a.ts";
export * from "./b.ts";
// mod.ts
export * from "./a.ts";
export * from "./b.ts";
// main.ts
import { toolA1 } from "./mod.ts";

toolA1();
// main.ts
import { toolA1 } from "./mod.ts";

toolA1();
#!/usr/bin/env -S deno run --allow-read --allow-write --allow-net --allow-run --allow-env
// transpile.ts
import { bundle } from "jsr:@deno/emit@0.46.0";

export const typescriptBundleAndWrite = async (
  filePath: string | URL,
  outFile: string | URL,
) => {
  const { code } = await bundle(filePath);
  await Deno.writeTextFile(outFile, code);
};

typescriptBundleAndWrite("./main.ts", "./main.js");
#!/usr/bin/env -S deno run --allow-read --allow-write --allow-net --allow-run --allow-env
// transpile.ts
import { bundle } from "jsr:@deno/emit@0.46.0";

export const typescriptBundleAndWrite = async (
  filePath: string | URL,
  outFile: string | URL,
) => {
  const { code } = await bundle(filePath);
  await Deno.writeTextFile(outFile, code);
};

typescriptBundleAndWrite("./main.ts", "./main.js");
If I chmod +x transpile.ts and then run it: ./transpile.ts, I get the following js file: 
const toolA1 = ()=>{
    console.log("Tool 1");
};
toolA1();
const toolA1 = ()=>{
    console.log("Tool 1");
};
toolA1();
All good then! Just for extra reassurance, I also tested: 
// main.ts
import * as tools from "./mod.ts";

tools.toolA1();
// main.ts
import * as tools from "./mod.ts";

tools.toolA1();
And it outputs the exact same JS file. I hope this is reassuring to the next person too! This thread is resolved, thank you Deno discord for being my rubber duck

Did you find this page helpful?