Hi Paul,
Thanks for trying to help out with this feature.
I think GitHub is best used for discussion about changes to the actual code; higher-level questions around whether a specific change should be made to the application or any problems following the Readme steps for compiling the code are best had on this forum. There’s currently no specific area of the forum for discussing build errors because it’s not something that happens often enough to justify the segregation.
I don’t recognise those error messages you’ve posted. It’s possible that whichever commit you are trying to build is no longer compatible with some of the auto-updating dependencies in package.json. If that’s the only problem then you should find that npm install ci will get you exactly the same versions that work for me or the CI server.
In this specific case though, I have already implemented the relevant code as part of the feature-save-password-2019 branch. You’ll see there is a lot of work in progress on that branch so it’s not yet ready for collaboration I’m afraid.
I’m working on the ideas I presented in Entry (password) saving improvements coming soon earlier this year and hope that I’ll have the branch in a state ready for my own testing and private use within a couple of weeks. After that there’s a fair bit of code tidy up to do and enabling localisation of the new strings, at which point it should be ready for beta testing and therefore merging into master. Please feel free to offer any feedback on the plan in that forum post and stay tuned for opportunities to help me refine the feature during the beta testing period 