jscodeshift icon indicating copy to clipboard operation
jscodeshift copied to clipboard

A JavaScript codemod toolkit.

Results 101 jscodeshift issues
Sort by recently updated
recently updated
newest added

If the transform is async, defineTest run error, because the defineTest only support sync, output is promise

Allow syntax like `import obj from "./something.json" with { type: "json" };`

CLA Signed

Is it possible to use jscodeshift to modify `.d.ts` files? I'm trying to parse a file that looks like this: ``` import * as runtime from '@prisma/client/runtime/index'; declare const prisma:...

How do I get a hold of the collection for `@Directive()` and `@ObjectType()` and `Field()` decorator calls in this example? https://astexplorer.net/#/gist/96fa2a58a3c859d61278839d7b897f8f/acf963ec5bd8c96799d87bf4f8ccf6504c24c6d6 I have tried ```js module.exports = function transformer(file, api)...

question

It looks like jscodeshift does not currently support the accessor keyword that was added typescript in 3.9. Can we please add support for this. Thank you. https://github.com/microsoft/TypeScript/pull/49705 https://github.com/tc39/proposal-decorators

upstream

I'd like to list some topics that need to be visited in order to bring jscodeshift out of stagnation. 1. The biggest issue is with recast. This library hasn't really...

discussion

`applyTransform` relies on `testOptions` for a `parser` option. At the same time `defineSnapshotTestFromFixture`, `defineSnapshotTest`, `runSnapshotTest` (maybe others) don't propagate user-supplied `testOptions`. A possible work-around is to run export the parser...

When debugging via the VSCode on Windows 11, I got the following error: ``` Uncaught SyntaxError C:\~~\node_modules\.bin\jscodeshift:2 basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')") ^^^^^^^ SyntaxError: missing ) after argument...

CLA Signed

I want to transform this ```jsx const obj = { a: 'a', b: 'b', c: 'c', d: 'd', } ``` into this ``` const obj = { a: 'a', b:...

Now I have to iterate comment nodes and modify values, but comment's signature is staying untouched. In: ``` // leading_comment const definition = 'string' /* block_comment */ ``` Modification: ```...

question