Cannot find module if create with source and api-module parameters
See original GitHub issueI use command claudia create --region us-east-1 --api-module lambda --source ./build/src
, it throws error cannot find module build/src/lambda
. The reason is create command use require(path.join(source, apiModule)) to find module, which will discard ‘.’.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How do I resolve "Cannot find module" error using Node.js?
Using npm install installs the module into the current directory only (in a subdirectory called node_modules ). Is app.js located under ...
Read more >CommonJS modules | Node.js v19.3.0 Documentation
In order to make modules available to the Node. js REPL, it might be useful to also add the /usr/lib/node_modules folder to the...
Read more >Module Methods - webpack
This section covers all methods available in code compiled with webpack. When using webpack to bundle your application, you can pick from a...
Read more >Modules | NestJS - A progressive Node.js framework
The @Module() decorator provides metadata that Nest makes use of to organize ... Nest uses to resolve module and provider relationships and dependencies....
Read more >cannot find module 'process' or its corresponding type ...
If you just use the variable without an import statement, you get the error: Cannot find name 'process'. Do you need to install...
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
You may also get this error if you’ve put dependencies in the
dev-dependencies
with--save-dev
.I’m guessing that we should use the
--no-optional-dependencies
flag to get around this.fixed. thanks.