pwa-module VS commitlint

My go-to is https://pwa.nuxtjs.org/ + pwabuilder. You can have the barebones scaffolding made in 1 minute. Then just add your custom UI/logic, and deploy, and point the PWA Builder at the deployed Nuxt site, and it will generate your App store package.

In terms of stack I would recommend taking a look at Vue and Nuxt. There is a PWA module for Nuxt, which handles everything for you, so you literally only need to add 5 lines of config (implementing service workers yourself can be tedious).

Note that if your original project is built with Nuxt (a Vue meta-framework), you have a better-suited solution readily available in the Nuxt PWA module. Nuxt and its ecosystem of plugins are a bit much to tackle in the scope of this post, but the same PWA general principles we’ll cover here apply there, too. The difference is how the config options are entered. So, while the concepts translate, if you’re using Nuxt, I’ll refer you to the Nuxt PWA module docs for the details.

Documentation

The stack behind Journalistic is Django and Nuxt. The nuxt/pwa module takes care of everything PWA-related on the app side: manifest, service worker, etc. Easy peasy.

It's Nuxt.js with @nuxtjs/pwa, BTW.

Nuxt.js modules: Progressive Web App (PWA)

Apart from these we also need to enforce standards for all our commit messages(commit-lint).

There are many features of commitlint that I can't mention one by one, as well as installation guide. To know the detail you can directly access https://github.com/conventional-changelog/commitlint.

These commit message prefixes can help to provide context and organization in a project's version control history, making it easier to understand and track changes over time. Note: if you want to force these rules on commit messages, here is a commit linting lib for you. Commitlint

Commit Lint

I personally find it quite useful to enforce a uniform commit style. commitlint pairs well with husky.

⧗ input: Set up Conventional Commits using Husky and commitlint ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint husky - commit-msg hook exited with code 1 (error)

Can setup tools like Commitlint to add hooks that will reject a commit message if it is invalid, but if you format a commit message incorrectly it simply closes the commit buffer and returns to git status, meaning you have to retype out your commit message, which is obviously less than ideal.

✅ Angular 14 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with TestCafé ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with source-map-explorer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting