feat: cache invalidation on .babelrc update

[mellyeliu]

What changed / motivation ?

Let's add cache invalidation on .babelrc config update

• Iteratively search upwards through the file hierarchy until we find the closest .babelrc file
• Hash file and add to cache

Testing

Added tests writing .babelrc update

Pre-flight checklist

• I have read the contributing guidelines
  Contribution Guidelines
• Performed a self-review of my code

[github-actions]

workflow: benchmarks/size

Comparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.

@stylexjs/[email protected] size:compare
./size-compare.js /tmp/tmp.ChA3UN45FI /tmp/tmp.JqW7IvfaUF

Results	Base	Patch	Ratio
stylex/lib/stylex.js
· compressed	729	729	1.00
· minified	2,541	2,541	1.00
stylex/lib/StyleXSheet.js
· compressed	1,266	1,266	1.00
· minified	3,776	3,776	1.00
rollup-example/.build/bundle.js
· compressed	567,110	567,110	1.00
· minified	10,232,512	10,232,512	1.00
rollup-example/.build/stylex.css
· compressed	100,628	100,628	1.00
· minified	755,718	755,718	1.00

[nmn]

One nitpick before I merge this.

[nmn]

Don't use fs.access. Use fs.exists instead. That returns a boolean and won't throw an error.

[mellyeliu]

https://nodejs.org/api/fs.html#fs_fs_exists_path_callback fs.exists is deprecated and may cause issues with modern node versions. if error specificity isn't a concern we can use fs.exists but it might require updates later, which could impact maintainability

[nmn]

Also needs to be rebased.

[nmn]

This PR is still not ready to merge. It has a bunch of extra commits from other PRs that have already merged. I think it needs to be rebased.

[mellyeliu]

this should be safe to merge, iirc when you squash, it commits only the changes seen in the file diff. so even though the commit history of the PR is wonky, Github is aware of the latest state of origin/main.