The endpoint do work without running the debugger

have anyone seen a similar error?

If you head over to the file in the stack trace

C:\Users\camil\Desktop\Temis\temis-core\services\rest-api\node_modules\@serverless-stack\cli\scripts\start.js

and around line 971, you should see

const lambda = spawn(..

That's trying to spawn a

bootstrap.js

file which will import your lambda handler

./src/lambda.handler

It seems the

spawn

failed with the error

EBADF: bad file descriptor, uv_pipe_open

and the

exit

callback was invoked right away.

Let me take a look at this build issue.

@John Nguyen thanks! That's a great option, but it will be good if we can make it work for windows users OOTB.

Here is my setup:

node v12.13.0
npm v6.12.0
PowerShell 5.1.14393.3866

I ran

winver

in PS and it says "Windows Server 2016 Datacenter".

What did I try:

npx create-serverless-stack@latest my-sst-app
cd my-sst-app
npx sst build
npx sst start

I was trying to compare the terminal output I got vs ur screenshot for

sst build

, I noticed the extra slash in your handler

Here's what I see in the my PowerShell output:

Can you try out the steps I tried above and see if you run into issues?

npx create-serverless-stack@latest my-sst-app
cd my-sst-app
npx sst build
npx sst start

So the problem is related to the

defaultFunctionProps

. If I use the

srcPath

it fails, but if I just define the full path in the routes it works. (I was following the example here https://docs.serverless-stack.com/constructs/Api#specifying-function-props-for-all-the-routes)

Still having the issue when doing

yarn start

though

This works:

npx create-serverless-stack@latest my-sst-app
cd my-sst-app
npx sst build
npx sst start

Going to try the Typescript example (which is the one that I'm using)

Yep, also worked, might be something in my monorepo config

The issues I'm getting with the typescript monorepo are most likely related to a setting on my end

I will let you know if I manage to fix them

Although I still have this problem with the starter project https://serverless-stack.slack.com/archives/C01JG3B20RY/p1613389644159700

Is that right?

Do you think you can share a stripped down version of your monorepo setup with the

sst start

issue? I can try to reproduce it on my windows setup.

done

i see

srcPath

is currently commented out

@Frank So the

yarn start

issue only happens when trying it inside a monorepo. I tried different configurations (js and ts) but both throws the same error. I based the monorepo on this one https://github.com/AnomalyInnovations/serverless-lerna-yarn-starter but also other configurations, but with no luck. I haven't been able to pin point the problem, but I will let you know if I find something. Are you able to run it on your side inside a monorepo?

let me know if I can help! We really want to start using SST and Seed in our projects

Aight I managed to reproduce the

build

command issue.

This works:

srcPath: "src"

srcPath: "src/"

works on mac/linux, but fails on windows

we would need to handle path building better for windows

Let me take a look at the

start

command issue now.

Have you seen this issue before?

===================
 Starting debugger
===================

Transpiling Lambda code...
Debug session started. Listening for requests...
Error: Failed to load plugin '@babel' declared in 'BaseConfig': Cannot find module '@babel/eslint-plugin'
Require stack:
- /Users/frank/Sites/fwang/temis-core/services/rest-api/__placeholder__.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
    at Function.resolve (internal/modules/cjs/helpers.js:94:19)
    at Object.resolve (/Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/shared/relative-module-resolver.js:28:50)
    at ConfigArrayFactory._loadPlugin (/Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/config-array-factory.js:1017:39)
    at /Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/config-array-factory.js:908:33
    at Array.reduce (<anonymous>)
    at ConfigArrayFactory._loadPlugins (/Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/config-array-factory.js:904:22)
    at ConfigArrayFactory._normalizeObjectConfigDataBody (/Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/config-array-factory.js:725:44)
    at _normalizeObjectConfigDataBody.next (<anonymous>)
    at ConfigArrayFactory._normalizeObjectConfigData (/Users/frank/Sites/fwang/temis-core/node_modules/@eslint/eslintrc/lib/config-array-factory.js:665:20) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/frank/Sites/fwang/temis-core/services/rest-api/__placeholder__.js'
  ],
  messageTemplate: 'plugin-missing',
  messageData: {
    pluginName: '@babel/eslint-plugin',
    resolvePluginsRelativeTo: '/Users/frank/Sites/fwang/temis-core/services/rest-api',
    importerName: 'BaseConfig'
  }
}

but adding the module seems to solve it

Here is a simpler implementation without the noise of TS and other packages. It gives the same

start

issue

And I still get the

EBADF: bad file descriptor

error

I'm cross checking the project structure against the clean sst project and trying to spot a different.

It seems to be an yarn issue on windows

Could you help me verify that this causes the same problem for you:

npm init serverless-stack@latest my-sst-app --use-yarn
yarn start

@Camilo Rios I created a test release with the fix. Change

@serverless-stack/cli

and

@serverless-stack/resources

to version

0.9.3-next.1

in your package.json.

This should fix both the

build

issue when

srcPath

is specified; and the

EBADF: bad file descriptor

issue when running

yarn start

Let me know if it works for you, and I will cut an official release.

@Frank its now working on a monorepo without Typescript (build and start issues), thanks!!! In the typescript monorepo its not able to find typescript, I will check if its something on my end

I did a fresh install but its still failing to find typescript

I will keep looking

Could you try that and see if it works in a non-monorepo setup?

yes, it worked in a non-monorepo setup. The problem with the monorepo setup is that its trying to look for the tsc bin in the service folder.

I'm trying

yarn start

now

also working! Thanks @Frank for all the help!!

I will keep testing to see if I can break it again and understand what's going on

Just released v0.9.3 https://twitter.com/ServerlessStack/status/1361760631142178819