Hi, we discovered some problems with the current versions of sst (I just upgraded from 0.53 to 0.60) and yarn 3: 1. Every time a lambda is invoked in debug mode (

sst start

) for the first time the console is printing strange messages

[Module: null prototype] {
  default: { handler: [Getter] },
  handler: [AsyncFunction: handler]
} handler

…

[Module: null prototype] {
  ALGORITHM_IDENTIFIER: undefined,
  ALGORITHM_IDENTIFIER_V4A: undefined,
  ALGORITHM_QUERY_PARAM: undefined,
  ALWAYS_UNSIGNABLE_HEADERS: undefined,
  AMZ_DATE_HEADER: undefined,
  AMZ_DATE_QUERY_PARAM: undefined,
  AUTH_HEADER: undefined,
  AWS_DEFAULT_REGION_ENV: undefined,
  AWS_EXECUTION_ENV: undefined,
  AWS_REGION_ENV: undefined,
  AccountInfo: undefined,
  AdaptiveRetryStrategy: undefined,
  ArchivalSummary: undefined,
  AssumeRoleCommand: undefined,
  AssumeRoleRequest: undefined,
  AssumeRoleResponse: undefined,
  AssumeRoleWithSAMLCommand: undefined,
  AssumeRoleWithSAMLRequest: undefined,
  AssumeRoleWithSAMLResponse: undefined,
  AssumeRoleWithWebIdentityCommand: undefined,
  AssumeRoleWithWebIdentityRequest: undefined,
  AssumeRoleWithWebIdentityResponse: undefined,
  AssumedRoleUser: undefined,
  AttributeDefinition: undefined,
...

2.

sst update

does not work. Nothing gets updated 3. Seed sometimes complains about the yarn.lock file being updated during a yarn install, which is not the case. This seems to be a caching issue, since a complete redeploy fixes the problems. This only happens when I promote a from one stage to another. We downgraded to yarn 1 again for now. Edit: Only problem 1 is related to the sst version. It’s not happening in 0.53. Problem 2 and 3 have probably always been there under yarn 3.

Hey @Fabian Ehringer, for 1 @thdxr is working on a fix. For yarn 3, @thdxr know more about it, I will let him chime in as well.

Hey 1 was already fixed in the latest sst

Thank you 🙂 Do you guys recommend to use yarn berry or is it better to stick to yarn 1 for now? @Frank @thdxr

SST currently doesnt support Pnp mode. I’ve seen ppl got it to work with

nodeLinker: node-modules

I suggest sticking to yarn 1

Alright, thanks. With no Pnp support the benefits are limited anyways, I would say 🙂