Sample
lodash-es 4.18.1: Import single functions via direct subpaths from lodash-es requiring explicit .js extension and default import syntax in Node ESM
Verified sample for npm lodash-es 4.18.1: Import single functions via direct subpaths from lodash-es requiring explicit .js extension and default import…
sha256:a43406c2cb7a7a820569e638a3f025694c0eddfd843f544a9ade4a5f9b27c47d
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
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-16 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Import single functions via direct subpaths from lodash-es requiring explicit .js extension and default import syntax in Node ESM
- Packages
- Symbols
-
- cloneDeep
- merge
- Environment
- node
- Created
- 2026-08-16T07:07:31Z
Contract
- import direct subpath functions from lodash-es requiring explicit .js extension
- import subpath modules using default import syntax because submodules only export default
- verify extensionless subpath imports fail with ERR_MODULE_NOT_FOUND in Node ESM
- verify submodule named exports do not exist on subpath files
- assert cloneDeep and merge perform deep cloning and merging correctly
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs