Trivikram Kamat

https://github.com/Budibase/budibase/blob/cb11a1609136ff8a165143fa97c6bb39cbdc17e8/packages/server/src/integrations/dynamodb.ts#L12

This happens as jscodeshift does nor detect TSQualifiedName inside NewExpression, like the following: ```ts const arr = new Array(); ``` But it detects TSQualifiedName in types as follows: ```ts const...

This appears to be a bug in JSCodeShift, as the following log clearly shows there's a TSQualifiedName for example input. Log: ```js console.log(source.find(j.NewExpression).nodes()[0].typeParameters.params[0].typeName.left); ``` Output: ```console Node { type: 'TSQualifiedName',...

This work can be resumed when upgrading eslint to v9

Blocked on https://github.com/import-js/eslint-plugin-import/issues/2556

Partially blocked on https://github.com/microsoft/vscode-eslint/issues/1644

Migrating to biome instead in https://github.com/aws/aws-sdk-js-codemod/pull/886

As of >0.25.0, we add a comment to assist tranform `retryDelayOptions` Example: https://github.com/awslabs/aws-sdk-js-codemod/blob/main/src/transforms/v2-to-v3/__fixtures__/config/retryDelayOptions.output.js

The `maxWaitTime` does not cause any performance issues. It's just a default value which is required in JS SDK v3 waiters. More details in https://github.com/awslabs/aws-sdk-js-codemod/issues/53#issuecomment-1366081340 Would adding the following comment...

The performance issues in waiters, if any, may be caused by retry behavior of waiters. Please create a [bug report](https://github.com/aws/aws-sdk-js-v3/issues/new?assignees=&labels=bug%2Cneeds-triage&projects=&template=bug-report.yml&title=TITLE+FOR+BUG+REPORT) on aws-sdk-js-v3 repo if you're seeing some concrete differences between...