0 60 4 `sst start` boots up as per normal but all functions Serverless Stack #help

(0.60.4) `sst start` boots up as per normal, but a...

Derek Kershner

01/21/2022, 4:08 PM

(0.60.4)

sst start

boots up as per normal, but all functions called through API routes (https) throw error

"Runtime.HandlerNotFound: /home/dkershner/repos/global-api-devops/.sst/artifacts/157a4603/src/api/health/get.default is not a function"

The file at that location appears to exist and contain uglified, but valid, code... I have tested 2 apps, and this persists to both.

Derek Kershner

01/21/2022, 4:09 PM

My console also isnt working, so I cannot try another method of invocation.

Derek Kershner

01/21/2022, 4:13 PM

I get the same error if I connect locally, then go into the AWS console and manually invoke the function.

thdxr

01/21/2022, 4:14 PM

Is this with esm turned on?

Derek Kershner

01/21/2022, 4:14 PM

no, the only difference is that I updated CDK and SST to the latest

thdxr

01/21/2022, 4:14 PM

can you send me the code in "Runtime.HandlerNotFound: /home/dkershner/repos/global-api-devops/.sst/artifacts/157a4603/src/api/health/get.default is not a function"

Derek Kershner

01/21/2022, 4:15 PM

its short and I dont mind folks seeing, since there is nothing in it

Derek Kershner

01/21/2022, 4:15 PM

Copy code

var __defProp = Object.defineProperty;
var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
var __getOwnPropNames = Object.getOwnPropertyNames;
var __hasOwnProp = Object.prototype.hasOwnProperty;
var __markAsModule = (target) => __defProp(target, "__esModule", { value: true });
var __export = (target, all) => {
  for (var name in all)
    __defProp(target, name, { get: all[name], enumerable: true });
};
var __reExport = (target, module2, copyDefault, desc) => {
  if (module2 && typeof module2 === "object" || typeof module2 === "function") {
    for (let key of __getOwnPropNames(module2))
      if (!__hasOwnProp.call(target, key) && (copyDefault || key !== "default"))
        __defProp(target, key, { get: () => module2[key], enumerable: !(desc = __getOwnPropDesc(module2, key)) || desc.enumerable });
  }
  return target;
};
var __toCommonJS = /* @__PURE__ */ ((cache) => {
  return (module2, temp) => {
    return cache && cache.get(module2) || (temp = __reExport(__markAsModule({}), module2, 1), cache && cache.set(module2, temp), temp);
  };
})(typeof WeakMap !== "undefined" ? /* @__PURE__ */ new WeakMap() : 0);

// src/api/health/get.ts
var get_exports = {};
__export(get_exports, {
  default: () => get_default
});
var handler = async () => {
  return {
    statusCode: 200,
    body: "OK"
  };
};
var get_default = handler;
module.exports = __toCommonJS(get_exports);
// Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {});
//# sourceMappingURL=get.js.map

thdxr

01/21/2022, 4:17 PM

how are you exporting the handler in the source?

thdxr

01/21/2022, 4:17 PM

is it a default export?

Derek Kershner

01/21/2022, 4:17 PM

correct

Derek Kershner

01/21/2022, 4:17 PM

Copy code

import { APIGatewayProxyHandlerV2 } from "aws-lambda";

const handler: APIGatewayProxyHandlerV2 = async () => {
    return {
        statusCode: 200,
        body: "OK",
    };
};

export default handler;

thdxr

01/21/2022, 4:17 PM

ah this may be what doesn't work now with the new runtime updates, I didn't think was ever supported

thdxr

01/21/2022, 4:18 PM

typically people do

export handler

but let me see if I can get defaults working again

Derek Kershner

01/21/2022, 4:18 PM

hmmm...its just a name seemingly... (

default

handler

)

Derek Kershner

01/21/2022, 4:18 PM

ill try named export

thdxr

01/21/2022, 4:19 PM

The runtime changes use

import

instead of

require

and I suspect

import

works differently and is conflicting with that ugly transpiled code

Derek Kershner

01/21/2022, 4:20 PM

oh, in that case it might, but I think you can still import default as named, like

import { default } from "...";

Derek Kershner

01/21/2022, 4:22 PM

you are correct, it is something to do with default exporting

Derek Kershner

01/21/2022, 4:23 PM

are you guys using

nodejs-lambda

under the hood? Would the problem be there?

Derek Kershner

01/21/2022, 4:28 PM

doesnt look like it.

thdxr

01/21/2022, 4:30 PM

I'm going to try and recreate the issue shortly - it's a combination of esbuild's output + aws-lambda-ric

Derek Kershner

01/21/2022, 4:41 PM

note that this is only locally, the functions actually work out in the wild (deployed)

thdxr

01/21/2022, 4:44 PM

yeah that makes sense because we're using a forked version of the production runtime

Daniel

01/21/2022, 9:02 PM

FWIW I just upgraded SST and CDK and am getting the same error. This is what my source export is:

export const handler = server.createHandler();

Daniel

01/21/2022, 9:03 PM

and this is what it looks like in the artifacts folder

Copy code

var handler = server.createHandler();
module.exports = __toCommonJS(api_exports);

Error message is:

Copy code

{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Runtime.HandlerNotFound: /Users/danielwise/bwcode/rmw-sst-app/.sst/artifacts/0fa3d328/src/api.handler is undefined or not exported"

thdxr

01/21/2022, 9:07 PM

I'm working through this now, a quick workaround is to use named exports

thdxr

01/21/2022, 10:38 PM

if you want the fix asap you can add @serverless-stack-slack/aws-lambda-ric@2.0.11 to your deps

thdxr

01/21/2022, 10:38 PM

Otherwise we'll be doing a release soon

Daniel

01/21/2022, 10:41 PM

thanks for your help!