Wow, someone has submitted Cypress.io here - probably because we just crossed 25k stars on GitHub.
We at Cypress do read these comments, and we definitely understand both the positive and negative opinions. If you have never tried Cypress yourself - take a look at the first test page https://on.cypress.io/writing-your-first-test
Try it yourself, you might like the syntax and the developer experience. And if not - no worries, there are TestCafe, Puppeteer, Playwright, Selenium, Webdriver that might work better for you.
Has links to blog / slides / github and list of GitHub projects with search. Allows people and myself to quickly find something. Getting recruiters' pitches (and occasional hand crafted emails to join teams) every day.
I have been using Dokku for a year for personal side projects and it has been awesome. Each release brings good features, fixes bugs and in general improves it.
I blog at https://glebbahmutov.com/blog/ as a reminder to myself how some problems are solved. Now people at work, especially new hires, comment how 50% of my communication or answering questions are just links to the blog posts.
That's why I recommend using PouchDB to work with whatever API is available. Storage limits are harder to work around, but if your HTML snapshot weights more than 50MB (or even 1MB!) that it is a problem by itself.
The app saves its state in whatever form it wants. The demo saves it in localStorage that is very limited. One really should look at something better like IndexedDB or WebSql (or something that hides the technical details, like localForage or PouchDB).
PS: Here is a little bonus, my current exploration where ServiceWorker might be useful - run your server (like ExpressJS) inside the ServiceWorker ;) https://github.com/bahmutov/express-service
Well, consider that you have not paid anything for these packages, can you complain that authors do not follow the semver?
If you want to protect yourself and upgrade reliably - there are tools, like my https://github.com/bahmutov/next-update - runs your tests and only keeps upgrades that don't break stuff.
I like asking a refactoring / functional programming question in JavaScript like this one http://glebbahmutov.com/blog/functional-js-interview-questio... trying to make the candidate work through several small steps. At each step (step itself is pretty simple) I am looking for clarity and the candidate being able to explain the logic and the solution.
We at Cypress do read these comments, and we definitely understand both the positive and negative opinions. If you have never tried Cypress yourself - take a look at the first test page https://on.cypress.io/writing-your-first-test
Try it yourself, you might like the syntax and the developer experience. And if not - no worries, there are TestCafe, Puppeteer, Playwright, Selenium, Webdriver that might work better for you.