Releases: facebook/jscodeshift
Releases · facebook/jscodeshift
v17.2.0
v17.1.2
v17.1.1
17.1.0
[17.1.0] 2024-10-30
Added
pkg.pr.new
will now be used to build an npm pakage for each commit to the repo, allowing you to more easily test changes or use new features before an official release is cut. (#622, @Aslemammad)
Changed
Fixed
- Removed old
docs
command frompackage.json
since the new docs are in thewebsite
folder, which has instructions in its README.
17.0.0
[17.0.0] 2024-08-06
We needed to go from v0.x to a major release, and it may as well happen now. jscodeshift has been around for nine years though, so going to v1.0.0 didn't feel quite right. I've instead promoted the minor version number to a major version number, similar to what React did when it went from 0.14 to 15.0.
Fixed
- Node.js 16 is now explicitly specified as the minimum required version. It was already required due to some dependencies requiring it, but this makes it explicit (#607, @trivikr)
Added
- A new jscodeshift website has launched, thanks to the team at Codemod. (#592, @mohab-sameh with some tweaks by @morinokami)
- Added collection functions for import declarations, including finding imports and inserting new imports (#617, @danieldelcore)
Changed
0.13.1
Changed
- Switched from
colors
tochalk
to mitigate a security vulnerability incolors@1.4.1
.
Full Changelog: 0.13.0...0.13.1
v0.7.0
Added
Changed
- Moved from BSD to MIT license
Fixed
- No longer throw an error when calling jscodeshift on a non-existent path (#334, @threepointone)
- Preserve the original file extension in remote files (#317, @samselikoff)
v0.6.4
v0.6.3
v0.6.2
Changed
@babel/register
/@babel/preset-env
is configured to not transpile any
language features that the running Node process supports. That means if you use
features in your transform code supported by the Node version you are running,
they will be left as is. Most of ES2015 is actually supported since Node v6.- Do not transpile object rest/spread in transform code if supported by running
Node version.
Fixed
- Presets and plugins passed to
@babel/register
are now properly named and
loaded.