Topics created by lapinskyi98

Question is a little cryptic and I am a noob on this tool but increasing the timeout period to 1 minute (only needs ~30 seconds) and memory for my lambda to 1024 mb helped a lot. I have other issues related to FS on lambda so not a complete solution.

This isn't an actual error, you can just ignore it. Or disable scheduling extension if it is annoying.

{ .... "extensions": { "scheduling": { "enabled": false } } }

Your installation looks corrupted, try to delete node_modules folder and run npm install again.

Although not an issue likely, note that you have dependencies listed in package.json devDependencies node where it should be likely in dependencies.

See how the logger config looks in the tutorial
https://github.com/jsreport/jsreport-aws-lambda-starter-kit/blob/master/prod.config.json#L12

I found a solution

await JsReport({ //configFile: path.join(__dirname, './prod.config.json'), chrome: { launchOptions: { args: chromium.args, defaultViewport: chromium.defaultViewport, executablePath: await chromium.executablePath, headless: true, } },

----> headless: true