Unable to import module
See original GitHub issueHi,
the plugin does not work for me, from CloudWatch Logs:
Unable to import module '_warmup/index': Error at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.require (module.js:497:17) at require (internal/module.js:20:19)
Unable to import module '_warmup/index': Error
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
Does it only work if you are using nodejs runtime?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:34 (16 by maintainers)
Top Results From Across the Web
Resolve "Unable to import module" errors from Python ... - AWS
You typically receive this error when your Lambda environment can't find the specified library in the Python code. This is because Lambda ...
Read more >AWS error from Python: No module named lambda_function
This is one way to get rid of the "Unable to import module lambda_function " errorMessage. If you were to rename the handler...
Read more >Unable to import module lambda function No ... - Edureka
Hi@akhtar,. This error appears when you haven't named your code file or function correctly. You need to go to Lambda -> Functions ->...
Read more >"errorMessage": "Unable to import module 'otel_wrapper': No ...
"errorMessage": "Unable to import module 'otel_wrapper': No module named 'utils'" #254. Open. itaybaror opened this issue on Jun ...
Read more >Prisma cloud[ERROR] Runtime.ImportModuleError: Unable to ...
We are getting the following error in our Lambdas, [ERROR] Runtime.ImportModuleError: Unable to import module 'twistlock': Failed to import - 404799.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, just created a PR in Serverless that fix the root cause of this issue (the
individually
config is not honored when there is apackage: artifact: ...
set up at service level).Let’s see if it can get merge and we won’t need to workaround the issue 🙂
So how did you guys resolve the issue? Even with cleanFolder set false the issue still remains.