Create failing with ENOENT: no such file or directory
See original GitHub issueI’m trying to install on Windows, and whether I use cygwin or the native shell I run into this problem trying to create the service:
Jim-PC17 495 ~/workspace/jetsam$ serverless create -u https://github.com/adieuadieu/serverless-chrome/tree/master/examples/serverless-framework/ aws
Serverless: Generating boilerplate...
Serverless: Downloading and installing "examples\serverless-framework\aws"...
Serverless Error ---------------------------------------
Error: ENOENT: no such file or directory, link 'C:\Users\Jim\workspace\dist' -> 'C:\cygwin64\tmp\serverless-chrome\packages\lambda\integration-test\dist'
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Forums: forum.serverless.com
Chat: gitter.im/serverless/serverless
Your Environment Information -----------------------------
OS: win32
Node Version: 8.9.3
Serverless Version: 1.24.1
I’m new to this stack, and I’m not sure if that cryptic error message means it can’t make a symlink or can’t find a symlink, or if it’s suggesting I make one. What I have figured out:
- C:\Users\Jim\workspace\dist doesn’t exist (and probably shouldn’t be created, as it’s outside the directory I’m trying to install into).
- C:\cygwin64\tmp\serverless-chrome\packages\lambda\integration-test does exist but has no dist subdir.
- I see in github dist is supposed to be a symlink that points up the tree, but I don’t see its target in github. Maybe it’s supposed to be created during the install? I haven’t figured out how to turn on enough logging to follow the install process.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:12
- Comments:16
Top Results From Across the Web
yarn create failing with ENOENT: no such file or directory ...
Installed Yarn with both apt and npm -g and getting the same issue. I haven't tried with this with any creates other than...
Read more >ENOENT: no such file or directory when running npm ...
Open a terminal in your pc's root and run this command: killall node · Before restart the new metro bundler please reinstall the...
Read more >Package Manager: ENOENT: no such file or directory, mkdir
Description* Attempting to create or open a project when there is a quote in the project path/name or in the UPM cache path...
Read more >Error: ENOENT: no such file or directory, stat '/opt/ ...
I have a next error: Error: ENOENT: no such file or directory, stat '/opt/render/project/src/client/build/index.html My code here: if ...
Read more >How To Fix the “Enoent” Error?
The “enoent” can appear because of some missing files or usage of the relative path that can be solved by creating an expected...
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
Any updates on this?
Any workarounds for this? I’ve tried a few things, including:
Run in GitBash as administrator Gives same error as reported by @jkellyinsf
Run in PowerShell as administrator Gives same error as reported by @jkellyinsf
Clone the repo (git@github.com:adieuadieu/serverless-chrome.git) then
invoke local
version-info as administratorI had to install chrome-launcher - shouldn’t this be a dev dependency by default?
In any case, once chrome-launcher is installed, I get the following error:
I manually removed the
.webpack
directory and retried invoking the service locally, but got the same error. Here’s the full output:My next step will be to try to rebuild the version-info function from scratch to see if I can spot any issues or get it working.
Any other suggestions for diagnosing/fixing/working-around this issue?