middyjs / middy

🛵 The stylish Node.js middleware engine for AWS Lambda 🛵
https://middy.js.org
MIT License
3.7k stars 374 forks source link

✖ No "exports" main defined in ***i/node_modules/@middy/core/package.json #1215

Closed miladezzat closed 3 months ago

miladezzat commented 3 months ago

Describe the bug When I upgrade the version of middy from 4 to 5 give me the following error

✖ No "exports" main defined in ***/node_modules/@middy/core/package.json
✖ Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in ***/node_modules/@middy/core/package.json
      at new NodeError (node:internal/errors:405:5)
      at exportsNotFound (node:internal/modules/esm/resolve:366:10)
      at packageExportsResolve (node:internal/modules/esm/resolve:656:13)
      at resolveExports (node:internal/modules/cjs/loader:590:36)
      at Module._findPath (node:internal/modules/cjs/loader:664:31)
      at Module._resolveFilename (node:internal/modules/cjs/loader:1126:27)
      at Module._load (node:internal/modules/cjs/loader:981:27)
      at Module.require (node:internal/modules/cjs/loader:1231:19)
      at require (node:internal/modules/helpers:177:18)
      at Object.<anonymous> (***/lib/middlewares/apply-middleware.js:1:15)
Replying 502

To Reproduce How to reproduce the behaviour:

  1. Sample code const middy = require('@middy/core');
  2. Input '....'
  3. Unit test '....'
  4. Thrown error

Expected behaviour A clear and concise description of what you expected to happen.

Environment (please complete the following information):