- I wondered if you’d like to prioritize talking about the Node20 upgrade and leave the last 15 minutes to talk about Engineering Infrastructure at StateVoices?
- I put out an update in the #2023-hackathon, incymi: https://state-voices.slack.com/archives/C0663UYNJ9Z/p1701997103589609
- You’ll find all the helpful links to my current work and how we’re moving the needle forward.
- Some major highlights are:
- Migrating to version 3 standards of AWS (complete!)
- Migrating to version 3 of Apollo Client (still in the works)
- And Migrating from Recompose to (paused until Apollo Client is functional)
- Option A: React-Hooks refactor 35 files and major refactor of each document. This path is less desirable, but I have two folks trying it out to see if they can teach us the pattern for upgrading each page at industry standard.
- Option B: finding a replacement dependency that mimics the same behavior as Recompose This still has 35 files, but refactoring the functions to import correctly is a different technical lift outside of refactoring to establish react-hooks. This option needs the correct dependencies, and still has us relying on code is 1 year old instead of 3 years old. It’s a temporary fix to give us more time to refactor into React Hooks. This is the one I am working on. I am trying to transition to react-hooks-compose , but this update is paused until I complete the Apollo Client
Additional Points of Clarity:
- Each commit I make to this repository is transitioning on average between 300-3500 packages, all with dependencies that I have to individually add.
- The node20 update III branch is currently at 62 commits. All tests are failing until I have completed the above migrations for the application.
- Once I upgrade one dependency, I need to upgrade the remaining deprecations. So this process is about finding the next error and deciding the best steps forward. Each new commit will come with a new set of issues that need to be resolved, and I am documenting that work as best as I can.
- I will be meeting with Larry and Sky this week to continue this upgrading conversation. Please stay tuned for updates on that.
- 35 files must be updated to complete the Node20 upgrade, I am currently at 22 files upgraded.
- Most large feature requests are broken down to about 3-5 documents. So this is 7 times larger than a typical feature. Additionally, most products are upgrading from last year, and parts of the code that we rely on haven’t been upgraded in 3+ years, creating large dependency issues that cannot be anticipated until the error shows up in our terminal.
- This is difficult to explain, but I’m willing to answer any questions you may have. I will always provide a gist with my updated work…but these gists are more for me to track the various error messages I encounter. It is by default difficult to follow and read, but I am willing to support as best as I can in ensuring that you have the information you need. Please allow for some growing room as I switch between getting this done and sharing what has already been done.