Always used TypeScript parser options

[ijlee2]

Background

Until now, @codemod-utils/ast-javascript allowed end-developers to use a different set of parser options for JavaScript files. This, however, sometimes results in additional code (e.g. 'Literal' vs. 'StringLiteral') for early exits and in lint errors because a recast property may exist in one but not the other.

Going forward, the set for TypeScript will be used to handle both JavaScript and TypeScript files. This should be okay since TypeScript is a superset of JavaScript, and helps the invocations for @codemod-utils/ast-javascript and @codemod-utils/ast-template become even more similar. It will also help me simplify the main tutorial.

How to migrate

AST.traverse now accepts 0 arguments. Remove the 1st argument, then run pnpm test to see if you need to update the 2nd argument for traverse.

import { AST } from '@codemod-utils/ast-javascript';

type Data = {
  isTypeScript: boolean;
};

function transform(file: string, data: Data): string {
-   const traverse = AST.traverse(data.isTypeScript);
+   const traverse = AST.traverse();

  const ast = traverse(file, {
    // ...
  });

  return AST.print(ast);
}

In the example above, if data.isTypeScript isn't used by the 2nd argument for traverse, you can remove data from transform and run pnpm lint to find additional dead code in /src and /tests.

See #324 for additional changes in @codemod-utils/ast-javascript@v4.