chore(node): bump maximum node version to 20.9.0

[pac-guerreiro]

Details

This PR bumps the maximum node version to 20.9.0, so that when the node version used by Expensify app is bumped to 20.9.0 there won't be any compatibility issues.

Related Issues

Expensify/App#25824

Automated Tests

Manual Tests

1. Update package.json for E/App:

"react-native-onyx": "git+https://github.com/pac-guerreiro/react-native-onyx#687f3ff44ddd4c9b4e75335dc56760d310fd6ae6",

2. Do npm install
3. Build react-native-onyx locally and copy dist folder into E/App node_modules/react-native-onyx
4. Run the app

Author Checklist

• I linked the correct issue in the ### Related Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

Screen.Recording.2023-11-14.at.15.37.30.mp4

iOS: Native

Screen.Recording.2023-11-14.at.14.52.00.mp4

iOS: mWeb Safari

Screen.Recording.2023-11-14.at.15.21.28.mp4

MacOS: Chrome / Safari

Screen.Recording.2023-11-14.at.15.45.51.mp4

MacOS: Desktop

Screen.Recording.2023-11-14.at.16.00.19.mp4

[pac-guerreiro]

@dylanexpensify @roryabraham PR is ready for review

[pecanoro]

@pac-guerreiro It looks good but, can you add some screenshots showing that this update didn't break the whole thing?

[roryabraham]

Agree with @pecanoro, this change looks fine but we need some evidence that it was tested with E/App.

[pecanoro]

Please don't force push after the review has started, it's against our standard practices.

[pecanoro]

Also let us know when you have added screenshots and such so we can get a final review from a C+.

[pac-guerreiro]

Please don't force push after the review has started, it's against our standard practices.

@pecanoro Sorry, I did not know that! I'll be more careful next time!

[pac-guerreiro]

@pecanoro @roryabraham

I added the testing procedure I did to the manual tests section above and I added screen recordings of the app running on all devices except Android which is taking too much to build.

Once the Android build is done, I'll add the screen recording!