BugdrLog in
All problems
EasyJavaScriptBackend Engineer · cli · codemod · file-selection · node

Command-line default file selection

★ 0.0 (0 ratings)30 min0 engineers solved this

Your assignment

This is a toolkit for writing and running source-code transformations (codemods) over JavaScript and TypeScript projects. Its main entry point is a command-line tool in bin/ that parses options with a small argument parser in src/argsParser.js, then hands the option set to src/Runner.js. The runner expands the given paths, filters them by the configured file extensions and ignore patterns, and dispatches each file to a worker (src/Worker.js) that loads the transform, parses the file with the selected parser, and writes the result back unless a dry run was requested. Transforms are plain modules exporting a function that receives the file info and an api object with the parser-bound helper. Parsers live in parser/ and helpers in src/. Tests sit next to the code in __tests__ folders and run with Jest.

What the team is seeing

incident log
When I point the command-line tool at my TypeScript source files, it reports that no files were selected and leaves them untouched, even though I named them explicitly. My plain JavaScript files are handled without any trouble.

Acceptance checks 1

  • Check 1

Discussion is locked — log in and complete this problem to join the discussion and rate your experience.