Error on deploy after "Serverless: Injecting Headless Chrome..."
See original GitHub issueI am getting an error on deployment of the service right after the info Serverless: Injecting Headless Chrome...
. Error is:
Error --------------------------------------------------
ENOENT: no such file or directory, unlink '/home/user/application/service/.build/handler.js'
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Stack Trace --------------------------------------------
There is no .build or handler.js and I have no idea why it would assume that there is as there is zero configuration to that effect.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Serverless deploy issue with Headless chrome
HI I m using serverless-plugin-chrome with nodejs8.10. I am facing below issue when I am deploying using serverless deploy -v
Read more >When trying to deploy to aws-lambda Error: operation not ...
I am using puppeteer-core, @serverless-chrome/lambda and serverless-plugin-chrome to take screenshot following these articles(but instead of ...
Read more >serverless-chrome - Bountysource
Hello, I'm seeing this error when trying to run locally: $ serverless invoke local -f screenshot Serverless: Injecting Headless Chrome.
Read more >Headless Chrome: an answer to server-side rendering JS sites
The techniques in this article show how to use the Puppeteer APIs to add server-side rendering (SSR) capabilities to an Express web server....
Read more >@serverless-chrome/lambda - npm package | Snyk
Run headless Chrome/Chromium on AWS Lambda For more information about how to use this package see README · Security · Popularity · Maintenance...
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 Free
Top 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
I don’t think it’s related, I’m trying to run it locally with serverless offline and I have the same issue. my error message is not on the unlink but link:
Sorry for ressurecting this, but I only have one function on the lambda and I’m affected with the same issue. Any updates on this?