The update is actually a refactor, which means that I changed how the code works internally, but ideally you shouldn’t notice any changes. I’ve done some testing and everything appears to work but there’s a good chance I missed something. So this is just a heads up that there could be new bugs. If you notice any new problems, please let me know!
(Technical details for anyone who is interested: The Readlang front end code has been ported from a mix of jQuery, Backbone.js and Preact, to be almost 100% Preact now. The Backbone.js dependency is totally gone, and the only non-Preact view left is the oldest and hairiest part of the app responsible for the text you interact with on the reader page. I’ll get around to updating this too at some point. I’m hoping that this refactor will allow me to make future improvements faster and more reliably.)
That’s great to hear As a fellow developer I know how much pain it can be to work with legacy code and I appreciate that you take the time to modernize things
When add a new word by searching, I can not generate a sentences by click “generate” button on Add New Word page. I need to add word firstly into list. Then click that word and generate again.
Click two adjacent words separately on reading page, it will automatically become a phrase. Before I need to click and drag to select.
Another thank you from me for you ongoing work on Readlang. I’m reading much more consistently on Readlang this year compared with last and I can’t believe how quickly my Swedish is improving.
This is probably unrelated, as I’d need to run your description of what you did through Readlang to have any hope of understanding it! However, in the past couple of days, I’ve had problems with the AI context explanations. It’s fine if I am just checking the definition of a word and if I only do that during a reading session then everything loads fine. But if I ask the AI a question to better understand that definition (e.g. I often ask for other sentences containing that word, or about the etymology) then the answer to that question sticks around even when I’m checking the meaning of other words. For some reason, that then makes the explanation of subsequent words load really slowly (as in, I can see it appearing line by line).
It’s certainly not a disastrous issue, but I do find it a bit jarring and thought I’d mention it in case it is connected with your updates.
when the book/file is read to the end=finished – and I want to delete the corresponding audio – there is no such option as an audio tab, but there is a youtube tab. once having the book/file closed and opening it up once again – the audio tab is there and can be deleted.
As a fellow developer I know how much pain it can be to work with legacy code and I appreciate that you take the time to modernize things 
