Sample
lodash 4.18.1: Import a CommonJS-only package from an ES module without the named-export or require-is-not-defined errors
Verified sample for npm lodash 4.18.1: Import a CommonJS-only package from an ES module without the named-export or require-is-not-defined errors. The…
sha256:e991b2b17774ff91d87fbe5ebfa2b3997a9f8b8c1fae7cb5d671573c6ebe68a9
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 5
- Signing keys that built it
- 2
Declared environment
node 22 linux x64 node 22 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-13 |
| node 22 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-13 |
| node 22 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-13 |
| node 22 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-13 |
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-17 |
Case
FIX- Goal
- Import a CommonJS-only package from an ES module without the named-export or require-is-not-defined errors
- Packages
- Symbols
-
- createRequire
- import.meta.url
- lodash.chunk
- lodash.groupBy
- lodash.merge
- require.resolve
- Environment
- node 22
- Created
- 2026-08-13T14:19:47Z
Contract
- importing a named export from the CJS-only package throws SyntaxError: Named export 'chunk' not found ... is a CommonJS module
- calling require() in ES module scope throws ReferenceError: require is not defined in ES module scope
- the default-import interop pattern returns correct lodash results for chunk, groupBy and a deep merge that does not mutate its input
- createRequire(import.meta.url) supplies real require semantics: it requires a JSON subpath inside the dependency and resolves the package to a filesystem path
- import * as namespace leaves the CJS functions undefined on the namespace and reachable only through namespace.default
Files
- csx.json
- package-lock.json
- package.json
- src/broken-named-import.mjs
- src/broken-require.mjs
- src/index.mjs
- test/contract.mjs