I'm a newbie in NodeJS and I'm not really familiar with all this thing of "npm". I mean, I didn't expect that just for one "npm install" I will get 10Mb of 30 different folders.  After a bunch of minutes when I processed this fact, I just realize that there are a lot of junk in those folders. They are not "compiled", let's call it this way... There are "readme" files, source files, test scripts, example applications, docs and so on!!! Many of modules has duplications of another modules inside their folders. Like “inherits”, “core-util-is”, “tedious” etc. Modules inside modules, Karl! And inside them – another modules, that already exist in other modules in the project. Whaaaaat???!!! There is an example of one of them - I'm in "node_modules" and in "bl" folder, but there is another "node_modules" folder inside it as well as "test", "readme" and all this junk here. And all of

Lately I ran over this issue and I want to share with you how I got out of there:  C:\>npm i npm -g npm WARN npm npm does not support Node.js v14.17.0 npm WARN  npm  You should probably upgrade to a newer version of node as we npm WARN  npm  can't make any promises that npm will work with this version. npm WARN  npm  Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11. npm WARN  npm  You can find the latest version at https://nodejs.org/ npm ERR! cb.apply is not a function npm ERR! A complete log of this run can be found in: npm ERR!       %USERPROFILE% \AppData\Roaming\npm-cache\_logs\2021-05-30T14_58_58_367Z-debug.log  It was after I installed a latest version of NodeJS. Command  npm -v returned something like 6.*.* We've tried to reinstall NodeJS. We've tried to remove %USERPROFILE%\AppData\Roaming\npm-cache . We've tried to uninstall NodeJS (together with npm). We've tried to install NodeJS again. We've tried to reinstall graceful-f

This thing is not trivial and I didn't found any simple explanation about this. So that is  select an existing resource (eg. "users") click on "Actions" dropdown and select "Create Resource" in " Resource Name " put parameter name in curly braces (eg. {userid}) in " Resource Path " you should see read-only text " /users/ " and textbox for parameter write {userid} in this textbox and click " Create Resource " you should see a new branch in your API tree - /{userid} . Select it. click  "Create Resource"-"Create Method" and add ANY method there integrate it with Lambda function you alrteady used for ANY of this resource (don't forget check " Use Lambda Proxy integration ") select this new brand ANY method, go to "Method Request" and ensure that there is "userid" parameter in "Request Paths" section That is it. Now you should handle it in your Lambda (to