Fullchee Zhang

`wd` vs `z` `wd` lets you create **custom names** for directories. * So for example, you can do * `wd add fcore` * and then type * `wd fcore` to...

Or should UTF-8 BOM be supported?

I am willing to contribute as well but I'm not sure what there is left to do

Not ideal but the workaround I found (which might be helpful in figuring out the issue) was this ```js function App() { return Hello; } expect(app.style._values).toMatchObject({ "--my-property": "1", // string...

@fpapado @gnapse Do we want to release a new major release of `jest-dom@7`which still supports Node 14? We're upgrading `jsdom@16` to `jsdom@21` - => 5 breaking changes which might unwittingly...

It seems to be fixed in the latest versions of `jsdom` When I install jsdom v16 (the same version listed in the package.json dev dependencies), I can reproduce the issue...

I noticed that `jest-dom` v6 dropped support anything before Node 14 https://github.com/testing-library/jest-dom/releases/tag/v6.0.0 and the latest version of jsdom that supports Node v14 is v21 (v22 min Node version is v16)...

Yup! https://github.com/Fullchee/jsdom-stripping-aspect-ratio/tree/jsdom-v21-node-14 It looks it's fixed in v21! 🎉 Gonna create a PR!

I'm stumped 😞 It looks like the aspect-ratio test fails in the PR where I upgrade to `jsdom@21` https://github.com/testing-library/jest-dom/pull/584/files?w=1#diff-6006ecc8e0f5f628f890cb05deb67d73b6aa124dd95f8a718ab5d3dde88a96a0

JSDOM v22 drops support for Node 14 while jest-dom still supports Node 14 for the current (v6) version - https://github.com/testing-library/jest-dom/releases/tag/v6.0.0 Can we first create a PR that upgrades to Node...