That is strange I m not sure where the ws module is coming f Serverless Stack #help

Join Slack

That is strange, I'm not sure where the ws module ...

# help

thdxr

10/27/2021, 12:59 PM

That is strange, I'm not sure where the ws module is coming from I don't think we need that

thdxr

10/27/2021, 1:00 PM

Is there any default function props being set anywhere with ws as a nodeModule in the bundle

Dan Van Brunt

10/27/2021, 1:00 PM

I mean I’m nearly 100% sure I’m looking at the correct function.

Dan Van Brunt

10/27/2021, 1:03 PM

weird… looking at the package.json I see this…

Dan Van Brunt

10/27/2021, 1:03 PM

why is it pushing a stub file when I’m providing a handler

thdxr

10/27/2021, 1:03 PM

Oh wait this was downloaded from AWS? This means the func is still in sst start mode

Dan Van Brunt

10/27/2021, 1:04 PM

seems like it…. but I thought running

yarn deploy

flips it back to prod files?

thdxr

10/27/2021, 1:05 PM

Yeah it does. Are you sure it went to the right stage

Dan Van Brunt

10/27/2021, 1:07 PM

dev stage all day for me

Dan Van Brunt

10/27/2021, 1:07 PM

so yes?

thdxr

10/27/2021, 1:07 PM

I'm not sure, SST deploy definitely deploys your real code

thdxr

10/27/2021, 1:07 PM

Did you see the functions get updated?

Dan Van Brunt

10/27/2021, 2:23 PM

working now… I think there was actually an error that I was not seeing

Dan Van Brunt

10/27/2021, 2:44 PM

@thdxr hmmm… is there a trick to using

copyFiles

and the base handler? I can now see both files in the directory… but the lambda is erroring out with …

Copy code

{
    "errorType": "Runtime.HandlerNotFound",
    "errorMessage": "lib/constructs/ApiSite/lambda.handler is undefined or not exported",
    "stack": [
        "Runtime.HandlerNotFound: lib/constructs/ApiSite/lambda.handler is undefined or not exported",

thdxr

10/27/2021, 2:47 PM

Does that error go away when you remove the copyFiles field?

thdxr

10/27/2021, 2:47 PM

From what I'm seeing in that screenshot shouldn't be any issue, unless the handler isn't exported or something

Dan Van Brunt

10/27/2021, 2:49 PM

checking…. this is my settings….

Copy code

const apiSite = new sst.Api(this, 'ApiSite', {
      defaultFunctionProps: {
        bundle: {
          copyFiles: [{ from: './contentful-app-frontend/build', to: './build' }],
        },
      },
      routes: {
        'ANY /': 'lib/constructs/ApiSite/lambda.handler',
        'ANY /{proxy+}': 'lib/constructs/ApiSite/lambda.handler',
      },
    })

Dan Van Brunt

10/27/2021, 2:53 PM

still deploying…. but looking into the build folder I can see that by removing the copyFiles command the location of the handler changes back to the root.

Dan Van Brunt

10/27/2021, 2:54 PM

seems like copyFiles may be F’n with the handler location somehow?

Dan Van Brunt

10/27/2021, 3:06 PM

weird…. still getting

Dan Van Brunt

10/27/2021, 3:06 PM

Copy code

{
  "errorType": "Runtime.HandlerNotFound",
  "errorMessage": "lib/constructs/ApiSite/lambda.handler is undefined or not exported",
  "stack": [
    "Runtime.HandlerNotFound: lib/constructs/ApiSite/lambda.handler is undefined or not exported",
    "    at Object.module.exports.load (/var/runtime/UserFunction.js:144:11)",
    "    at Object.<anonymous> (/var/runtime/index.js:43:30)",
    "    at Module._compile (internal/modules/cjs/loader.js:1072:14)",
    "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)",
    "    at Module.load (internal/modules/cjs/loader.js:937:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:778:12)",
    "    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)",
    "    at internal/main/run_main_module.js:17:47"
  ]
}

Dan Van Brunt

10/27/2021, 3:07 PM

but the dir looks like ….

Dan Van Brunt

10/27/2021, 3:07 PM

now I’m confused

thdxr

10/27/2021, 3:09 PM

let me try to recreate

Dan Van Brunt

10/27/2021, 3:11 PM

hmmmm looking into the lambda code… it looks odd and I don’t see the handler

Dan Van Brunt

10/27/2021, 3:13 PM

and that is the src handler

thdxr

10/27/2021, 3:14 PM

I think I can see the handler in the code - I definitely see a

/frontend

in the code

thdxr

10/27/2021, 3:14 PM

But maybe turn off minification and see

thdxr

10/27/2021, 3:15 PM

Do you know for sure that

export default { handler }

syntax works? I don't typically export that way

Dan Van Brunt

10/27/2021, 3:15 PM

oh shit

Dan Van Brunt

10/27/2021, 3:15 PM

missed that

Dan Van Brunt

10/27/2021, 3:15 PM

no that looks wrong

Dan Van Brunt

10/27/2021, 3:15 PM

sec

Dan Van Brunt

10/27/2021, 3:16 PM

🤦‍♂️ hope that is it but also not…. cause that is embarrassing.

Dan Van Brunt

10/27/2021, 3:16 PM

odd that linter didn’t catch that

Dan Van Brunt

10/27/2021, 3:17 PM

def seeing some odd linting when functions are nested deeper than 1-2 directories in lib

thdxr

10/27/2021, 3:18 PM

It's technically valid, just when bundled by esbuild it interprets it differently

thdxr

10/27/2021, 3:18 PM

Copy code

const { handler } = require("./file")

Copy code

import { handler } from "file"

Slight difference which causes it to fail depending on how

file

is bundled

Dan Van Brunt

10/27/2021, 3:28 PM

I think that was it. No error this time

5 Views

Open in Slack

Previous Next