ENOENT: no such file or directory, lstat '/Users/me/project-name/.build/.serverless'
See original GitHub issueWhen running serverless package (and serverless deploy) I get an error when using serverless-plugin-chrome:
ENOENT: no such file or directory, lstat '/Users/me/project-name/.build/.serverless'
If I comment out the plugin from my serverless.yml serverless package works without issue (but no headless chrome).
I tried downgrading to older versions of serverless, but got the same error.
# serverless -v
1.17.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Serverless deploy fails with ENOENT: no such file or directory
I get a strange error message when deploying my lambda function: $ serverless deploy Serverless: Bundling with Webpack.
Read more >Error: ENOENT: no such file or directory, when trying to import ...
I tried adding a new rule for ejs files in the webpack.config.js file. const slsw = require('serverless-webpack'); const nodeExternals = ...
Read more >Installing the AWS SAM CLI - AWS Serverless Application Model
This section describes how to install the AWS SAM CLI on macOS, Windows, and Linux.
Read more >Top 10 Serverless Deployment Errors (and How to Fix Them)
Deletes often fail if one of the resources to be deleted is protected, such as a non-empty S3 Bucket, or if it has...
Read more >serverless-esbuild - npm
Serverless plugin for zero-config JavaScript and TypeScript code bundling using extremely fast esbuild. Latest version: 1.35.0, last published: 33 minutes ...
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

Hi @momer @Jud
The plugin order is also important.
serverless-plugin-typescriptmust come beforeserverless-plugin-chrome. However,serverless-webpackmust come afterserverless-plugin-chrome. I’ve made sure thatserverless-plugin-chromeworks withserverless-plugin-typescriptbut have not yet had the chance to fully test withserverless-webpack—although it did work at once point. Still a bit of work to do to get all these parts to v1.0.@Jud @adieuadieu When I switched from webpack to
serverless-plugin-typescriptthis issue went away for me. Pretty much a drop-in replacement, but ideally this would work with both plugins