Wisen Tanasa

@laconiajs/core-contributors Any input on the design above? This is one of the feedback I've got from our users.

I'm facing this issue as well. I have downgraded nuxt from 2.14.7 to 2.14.0 and the error has disappeared. Seems like there may be internal variables that Nuxt-SEO has used,...

Tested and works against nuxt 2.14.0.

I have been using my own written workaround to handle such scenario. See ConditionalPlugin below. Any suggestion on how we can make this as serverless-webpack feature? ``` const ConditionalPlugin =...

@jamesdixon Unfortunately not. Might be able to help you if you can produce an MVCE.

@reestolonio Thanks for bringing this up! Are you stuck because of the version at the moment? I'll be away for 1-2 weeks, we'll appreciate pull requests as well if you...

@Ankcorn Suggested the usage of https://aws-lite.org/ as an alternative to upgrading AWS SDK. cc: @mpxr @tschoffelen

Thanks, Hugo. > V2 has [no EOL defined yet](https://docs.aws.amazon.com/sdkref/latest/guide/version-support-matrix.html) EOL is not directly for the SDK, but its relationship with AWS Lambda. [The EOL is defined here](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html), starting Aug 15,...

I briefly looked at [aws-lite performance metrics](https://aws-lite.org/performance#time-to-respond%2C-not-including-coldstart). It's unclear to me, but it seems that the limitation of the assessment is it doesn't compare against "AWS-SDKv3 Provided" scenario i.e. code...

Wow, thanks for doing all the analysis, Hugo! > aws (sdk2+sdk3+lite) P90¹ > high market share of sdk2 means most users would use sdk2 bundled, have sdk3 provided and if...