Indeed, the PR hadn’t been merged in yet, some review happened but no merge yet. Always review anything yourself and not just blindly use something so you can avoid unnecessary build headaches.
Sage 9 also runs a script on top of it that adds framework-specific (which can be selected) modifications.
See this discussion that also shows how to create a Sage project using the update branch:
Note: Changed Sage 9.2 to 9.1 (as 9.0.10 is the current release in master). Updated Sage 9.x You can now try out the Sage PR branch for webpack 5 and updated dependencies. The sage-installer which is used by Sage 9.x for adding framework support was also updated to add the right configuration and styles. Bootstrap 5 (Beta2) has been added for selection. Tailwind 2 is used now. Trying it out now! To prevent siloing of existing working forks of Sage 9 + (insert framework), please try this set…
You create a new Sage 9 project using that PR, then you overwrite all the files (except vendor/ and node_modules/ of your own project with the ones of the newly created Sage 9 (PR) project).
Then you can diff/merge everything, which means that you keep your own modifications but keep the new ones from the PR. Most modifications happened in the webpack-related configuration files (“glue”-code), so it shouldn’t be that much to adjust.