@Mischa Spiegelmock this incidentally fixes that absolute path problem

oh! excellent. will try to make time this week to try it

think you were experiencing some weirdest with the long path when bundled?

ok i just did a build.. the folders only have package.json

hm what's the srcPath and handler path again?

function configureLambdaDefaults(app: App) {
  const srcPath = "../../"

  // default function properties

  // merge default externalModules
  const externalModules = [
    "aws-sdk",
    "encoding",
    "@prisma/client/runtime",
    ...LAYER_MODULES,
    // TODO: from prisma layer
  ]

  app.setDefaultFunctionProps({
    srcPath,
    runtime: DEFAULT_RUNTIME_NAME,
    memorySize: 1024,
    timeout: "10 seconds",
    bundle: {
      minify: true,
      externalModules,
    },

appSync.createLambdaResolver({
      scope: this,
      handler: "packages/service/src/ats/api/graphql/interviewFormTemplate/addFormTemplate.addFormTemplate",
      typeName: "Mutation",
      fieldName: "addFormTemplate",
      functionOptions,
    })

the srcPath needs to be relative from where

sst.json

is

yea

ok let me dig into this

i can try moving SST up to the top level, i know that's how it's supposed to be, i had different problems before when i tried that but maybe it works now?

yeah the issue is SST also includes build tool type functionality and operates across your whole mono-repo so it's tough for us to support it isolated to a single package

ok, looks more promising

@thdxr Just got this error when running

npx sst update 1.2.16

from

1.1.x

Updating @serverless-stack/cli to 1.2.16
Updating @serverless-stack/resources to 1.2.16
/Users/xxxx/xxxxx/xxxxx/xxxxx/node_modules/@serverless-stack/cli/node_modules/@serverless-stack/core/package.json: ENOENT: no such file or directory, open '/Users/xxxxx/xxxxx/xxxxx/xxxxx/node_modules/@serverless-stack/cli/node_modules/@serverless-stack/core/package.json'

Running the command again works fine.