lodash types are wrong (or lying?)

[benasher44]

I'm not sure 100% what's going on (lodash's js style of exporting is not written in the most standard way — somewhat difficult to parse out in my head), but attw claims lodash's types are correct.

However, named lodash imports fail at runtime in node ESM. For example:

import { random } from "lodash";

This will fail with:

SyntaxError: The requested module 'lodash' does not provide an export named 'random'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:132:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:214:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
    at async loadESM (node:internal/process/esm_loader:34:7)
    at async handleMainPromise (node:internal/modules/run_main:113:12)

Node.js v20.10.0

[benasher44]

Maybe the issue is that the types are correct, but they're lying? If that's the case, feel free to close.

[benasher44]

I should add that they only fail when running node on ESM output. This import works fine with CJS output (only tested CJS using module set to node, not nodenext)

[benasher44]

Here's a simple program that illustrates the issue:

import _, { random } from "lodash";
console.log(_.random());
console.log(random());

This compiles fine with tsc --module NodeNext file.ts, but the import fails at runtime (am now wondering if I've discovered a bug with ts emit).

[benasher44]

Okay so I think I just stumbled upon microsoft/TypeScript#54018. Would it be reasonable to use cjs-module-lexer in this package, and then flag the types with 👺 ?

[andrewbranch]

Duplicate of #35? 😉

[benasher44]

Oh wow nice!