v0.3.16

Fixes

• Installation issue (missing module)
• Typo (process.std vs process.stdout)

v0.3.15

New

@iamdustan added supported for passing URLs to -t to load transforms remotely ( #94, #95 )

jscodeshift -t http://path/to/script.js

Note: That script cannot have any external dependencies, it has to be entirely self-contained.

Fixes

• Fix run-in-band ( #96, @zertosh )

v0.3.14

Improvements

@avikchaudhuri improved invalid symlink handling ( #92 ) and worker performance ( #93 )!

v0.3.13

Fixes

Ignore local .babelrc files. This fixes issues with running jscodeshift on code that was in a project that uses Babel. ( #85 ). Thanks to @sviridov!

v0.3.12

Fixes

Fixed filtering for .closest method ( #83). Thanks @juliankrispel!

v0.3.11

New

The --slient / -s option suppresses logging to the console ( #79 , #60 ).

v0.3.10

New

--run-in-band option makes jscodeshift execute all transformations in the main process instead of splitting up over multiple workers. Useful for debugging. (#71, @zertosh)

v0.3.9

Fixes

• Fixed promise (chain) returned by .run (#69). The code used to perform an invalid operation which let the promise fail always.

v0.3.8

Improvements

• jscodeshift.match and many methods that accept an object as second argument for filtering / pattern matching (e.g. .find) now also accept functions / objects containing functions. This allows you to write more complex filters more easily.

  Example:

  j(source)
  .find(j.VariableDeclarator, {id: node => node.name === 'foo' || node.name === 'bar'})

finds all VariableDeclarators whose identifier is either named "foo" or "bar".

Internal changes

jscodeshift switched to jest v0.5.10, which means that tests will only run in Node v4+. jscodeshift will likely continue to function in older Node versions though.

v0.3.7

New

• .run returns a promise that is resolved once all workers are done
• .at accepts negative indexes to get a collection of a node from the end of the current collection

Fixes

.remove now returns the collection itself