maybe for @thdxr - any idea why these imports are undefined in the out file? here's my `builder.ts`:

import SchemaBuilder from '@pothos/core';
import {
  DateTime,
  dateTimeParseValue,
  dateTimeSerialize,
} from './types/scalars';

export const builder = new SchemaBuilder<{
  Scalars: {
    DateTime: {
      Input: Date;
      Output: DateTime;
    };
  };
}>({});

builder.scalarType('DateTime', {
  serialize: dateTimeSerialize,
  parseValue: dateTimeParseValue,
});

...

the build is erroring with

dateTimeSerialize is not defined

(see screenshot for the out file)

Interesting. We're likely going to have a few issues like this before we harden our static analyzer. Let me see, it should have replaced the actual scalar with dummy ones

i'm getting a similar issue with defining objects through classes like in the pothos guide - not sure if it's related?

Yeah the static analyzer works by shaking away as much as possible so it can execute the js without issue. I hadn't tried it with classes yet so need to update it

cool - thanks man!

ok for scalars looks like I was only erasing

addScalaryType

and not calls to

scalarType

. Btw where are you importing that datetime scalar from?

cool, i will give that a go thanks! we have some other custom scalars too though

yeah I'll fix this

one last q for now - i've got a version of our existing API (which is apollo server running in a huge 1.5mb lambda) and currently it seems like our existing API is outperforming the SST ideal stack one (~200ms vs ~500ms for an identical request) - this is confusing since it looks like the sst lambda is way smaller (50kb)?! wondering if i've set something up wrong, have you noticed anything re performance with the ideal stack setup?

is this for sst start or for a deployed lambda?

sst start

hm that's confusing because the default apollo lambda boots up a full express server and pipes your aws lambda event through it

ace, thanks so much @thdxr

also curious why you're going the class route instead of using interfaces

migrating from typegraphql where most of our stuff is defined with classes, but i'm not married to them! just wanted to get something up and running quickly

That's what I figured, cool