Skip to content

[$125] Improve developer experience around react-compiler #48066

@Kicu

Description

@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 OwnerCurrent Issue Owner: @

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.ReviewingHas a PR in review

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions