Skip to content

"exports" feature produces incorrect output for multiple entry points #566

@Andreyco

Description

@Andreyco

Reproduction link or steps

Hello all!

Having multiple entry points for multiple platforms...

import {defineConfig} from "tsdown";

export default defineConfig([
    {
        entry: "./src/index.browser.ts",
        format: "esm",
        exports: true,
        platform: "browser",
    },
    {
        entry: "./src/index.node.ts",
        format: "cjs",
        exports: true,
        platform: "node",
    },
]);

Run

npx tsdown --config tsdown.config.ts

What is expected?

In this case, platform specific exports declarations.

Note: does not have to produce same output (this is manual declarations predating migration to tsdown)

"exports": {
        "node": {
            "import": {
                "types": "./dist/index.node.d.ts",
                "default": "./dist/node.js"
            },
            "require": {
                "types": "./dist/index.node.d.cts",
                "default": "./dist/node.cjs"
            }
        },
        "default": {
            "import": {
                "types": "./dist/index.browser.d.ts",
                "default": "./dist/browser.js"
            },
            "require": {
                "types": "./dist/index.browser.d.cts",
                "default": "./dist/browser.cjs"
            }
        }
    },

What is actually happening?

Results into malformed package.json file

{
  "name": "// redacted",
  "version": "// redacted",
  "description": "// redacted",
  "license": "UNLICENSED",
  "type": "module",
  "exports": {
    ".": "./dist/index.node.cjs",
    "./package.json": "./package.json"
  },
  "files": [
    "dist"
  ],
  "scripts": {
    // redacted
  },
  "devDependencies": {
    // redacted
  },
  "dependencies": {
    // redacted
  },
  "peerDependencies": {
    "@gohealth/analytics-events": "*"
  },
  "publishConfig": {
    "registry": "// redacted"
  },
  "main": "./dist/index.node.cjs"
}
",
  "module": "./dist/index.browser.js"
}

Any additional comments?

This seems to be a case where multiple entries for single platform would not be feasible - those work as expected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Priority

    None yet

    Effort

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions