[$125] Improve developer experience around react-compiler

[Kicu]

Version Number:
Reproducible in staging?: -
Reproducible in production?: -
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

This is purely a developer experience issue.

I have recently spent 1+ hours trying to fix an issue with react-compiler on one of my PRs. I think this may happen in future for more people and I wanted to add some tweaks to our code to improve this experience.

Here's what I would like to do:

• I will update our readme (https://github.com/Expensify/App/blob/main/contributingGuides/REACT_COMPILER.md) with one more case of handling react-compiler related error
• I will add a package.json script to run specifically this command on dev: npm run react-compiler-healthcheck &> output.txt (npm run react-compiler-healthcheck &> output.txt)
• instead of output.txt we would call this file something specific, for example react-compiler-output.txt
• finally add react-compiler-output.txt to gitignore, so that a developer can easily keep running the same script and not worry about accidentally pushing it to upstream repo (which I have - of course - did by mistake 😅)

I can have a PR ready very soon with these

CC @kirillzyusko

Action Performed:

N/A

Expected Result:

N/A

Actual Result:

N/A

Workaround:

N/A

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014befe13a62da3c50
• Upwork Job ID: 1828579678211382500
• Last Price Increase: 2024-08-28

Issue Owner

Current Issue Owner: @

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Current assignee @mallenexpensify is eligible for the NewFeature assigner, not assigning anyone new.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~014befe13a62da3c50

[melvin-bot]

Current assignee @rayane-djouah is eligible for the External assigner, not assigning anyone new.

[mallenexpensify]

Don't think we need ya here @shawnborton , sorry. I added NewFeature to create an Upwork job for @rayane-djouah .

[rayane-djouah]

@mallenexpensify The reward can be reduced to $125 according to the process, as PR doesn't require app testing.

[melvin-bot]

Upwork job price has been updated to $125

[mallenexpensify]

@rayane-djouah can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~014befe13a62da3c50

[rayane-djouah]

@mallenexpensify Accepted! Thanks!

[mallenexpensify]

Contributor+: @rayane-djouah paid $125 via Upwork

Don't think a regression test is needed here, plz comment if anyone disagrees and I'll reopen. And/or, @Kicu , if documentation needs to be updated anywhere. Thx