Remove @babel/* dependencies

[danbeam]

Hey @skovhus 👋 ! Me again.

Is there any reason why @babel/core and @babel/preset-env are in dependencies and not devDependencies?

It doesn't seem like they're consumed from production code anywhere. cc @lencioni

[codecov]

Codecov Report

Merging #356 (2dc05ee) into main (e4d0981) will decrease coverage by 0.10%.
The diff coverage is n/a.

❗ Current head 2dc05ee differs from pull request most recent head ae07f38. Consider uploading reports for the commit ae07f38 to get more accurate results

@@            Coverage Diff             @@
##             main     #356      +/-   ##
==========================================
- Coverage   92.19%   92.09%   -0.11%     
==========================================
  Files          26       26              
  Lines        1896     1872      -24     
  Branches      398      393       -5     
==========================================
- Hits         1748     1724      -24     
  Misses        102      102              
  Partials       46       46              

Impacted Files	Coverage Δ
src/transformers/sinon.ts	87.50% <0.00%> (-1.25%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[skovhus]

Is there any reason why @babel/core and @babel/preset-env are in dependencies and not devDependencies?

@babel/core is a peer dependency of @babel/preset-env which is is a peer dependency of jscodeshift. From my understanding the @babel/preset-env might not be needed as we are using fairly recent versions of node:

• Make @babel/preset-env optional, drop support for Node 8 and below facebook/jscodeshift#375
• fix: make @babel/preset-env optional facebook/jscodeshift#480

If that is true, then we should get rid of both @babel/core and @babel/preset-env.

[danbeam]

Is there any reason why @babel/core and @babel/preset-env are in dependencies and not devDependencies?

@babel/core is a peer dependency of @babel/preset-env which is is a peer dependency of jscodeshift. From my understanding the @babel/preset-env might not be needed as we are using fairly recent versions of node:

• Make @babel/preset-env optional, drop support for Node 8 and below facebook/jscodeshift#375
• fix: make @babel/preset-env optional facebook/jscodeshift#480

If that is true, then we should get rid of both @babel/core and @babel/preset-env.

Removing them is fine by me, as well.