Let’s break down the situation you are describing:
Good post, Lucas. I’ve seen version drift happen both before and after package-lock.json was introduced, and with yarn. Using `save-exact=true` is the best way to prevent this. The only time you may want to allow ranged version numbers is for peer dependencies.
From your question it sounds like “no build for UI” is a characteristic of the existing application that you would like to preserve. Both Svelte and Polymer can be used without a build step, but you don’t receive the full benefits of either framework when using this approach.
Interesting read, Mustafa. In my career I’ve worked across the spectrum of roles from developer to visual/interaction designer to UX researcher and back again.
The tension between conforming to native platform guidelines and grid systems vs being “creative” and innovating is, in my view, a sign that the digital designer…
Hi Gabe, you are correct — some of these optimisations (like service workers) would not materially benefit an application that is on-device. But the follow optimisations would still improve performance:
Hi Thulani, google the name of the web server you are using (such as IIS, Apache or ngnix) and the word “gzip”. For example, “IIS gzip”. I included a link that describes how to configure ngnix in the original post. If you are still not sure, search on StackOverflow.