Taylor Smock

Looking at https://github.com/jestjs/jest/issues/9324, it seems like there might be a test that is doing something wrong that might be causing the failure. I'm currently in the process of bisecting the...

Doing it manually will be a lot of work. I looked into it a bit awhile ago (sometime last year). I don't remember why I dropped it (it might have...

This was largely copied from #5721 so that we could build/run on Node 18+ without `NODE_OPTIONS=--openssl-legacy-provider`, so if #5721 is merged, that would remove the need for this PR. TBH,...

No, this PR is no longer relevant; the changes from this PR were in #5721.

~~@varun2948 : If you don't mind the failing frontend-code-test job, yes.~~ ~~I _think_ it should have been fixed by #6397. I did just rebase, and it is still failing.~~ EDIT:...

@manjitapandey : That should be fixed now.

It did. But I hadn't wiped the `node_modules` directory, so maybe there was a required component there. I'll debug and (probably) push a new yarn.lock file.

Well, `rm -rf node_modules && yarn install && yarn build` worked for me. Maybe there is a version issue? My tool versions are: * nodejs: 16.20.0 * yarn: 1.22.19

I was able to reproduce @HelNershingThapa's issue (from comment 2) with `rm -rf node_modules && yarn install && yarn build && yarn start`. The important bit was `yarn start`. I...

In other news, `yarn build` is giving the following message: ``` Creating an optimized production build... One of your dependencies, babel-preset-react-app, is importing the "@babel/plugin-proposal-private-property-in-object" package without declaring it in...