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

v0.3.6

Fixes

• Fix .closest not correctly applying filter argument (#41)

v0.3.5

Fixes

• File extension filter only applies to files in traversed directories, not to directly passed files
• Enforce latest recast version that fixes some printing issues
• Remove esprima-fb dependency

Changes

• Depend on babel-core instead of babel

v0.3.4

Fixes

• No worker spawned when using --cpu option.

v0.3.3

Fixes

• Printing options not passed along to root
• Trailing and leading whitespace being removed from file (#28)

v0.3.2

Fixes

• Really fixed install process