Does anyone get this error every now and then whil...
# sst
c
Does anyone get this error every now and then while the live lambda env is running?
Copy code
There was a problem reading the build metafile [Error: ENOENT: no such file or directory, open '/Users/dev/engine/.build/.esbuild.--src-graphql-server-handler.json'] {
   errno: -2,
   code: 'ENOENT',
   syscall: 'open',
   path: '/Users/dev/engine/.build/.esbuild.--src-graphql-server-handler.json'
}
happens somewhat randomly and I have to restart. Might be something with a jest watcher also running
npm test --watch
t
Hm I haven't seen that before
c
ill try to update this thread as I catch more clues
f
Does
npm test
run
sst test
behind the scene?
c
yep - turns into
sst test "--watch"
f
I see. Running 
sst test
would wipes out the 
.build
 folder and then creates it.
And
sst start
depends on the content in
.build
, think that’s causing the issue.
Can you try start up
npm test --watch
first, and then run
sst start
?
c
this seems to be working so far! Ill let you know if it happens again
f
Sounds good! Just created an issue for this https://github.com/serverless-stack/serverless-stack/issues/732