Hey there!
For the last few weeks, I have been participating in several interview process to get a new job and this resulted in doing several task assignements where I needed to build Vue/Nuxt application that was supposed to match certain criteria.
As I already have few good patterns and principles I like to implement in all my recent projects, I was doing repetitive work all the time copying the same concepts to a new project. And that is why I decided to create a small Nuxt Opinionated Starter where I have included all my repetetive work nicely grouped inside an easy to copy GitHub template.
If you would like to see the starter instantly, here is the link
Enjoy!
🟢 Opinionated Nuxt Starter
The main features of this starter are:
- Testing with Unit & E2E Setup
- Static code improvements with Linter/Prettier/Editorconfig
- Dockerfile for containerization
- Lighthouse CI for continous Software Quality audits (Performance, SEO, A11Y, Best Practices)
- Useful modules like Image, TailwindCSS, Security
- GitHub Actions Continous Integration script
By using it, you should have your project ready for deployment (Dockerfile), assuring great Software Quality (Testing, Lighthouse CI, GitHub Actions), secure (Nuxt Security), performant (Nuxt Image), and styled properly with TailwindCSS and Linters.
Definitely, this is not a ground breaking project that will revolutionize the web - more a starter that could help you start your new Nuxt projects faster with few recommendations from my side ;)
You can see the starter here.
📖 Learn more
If you would like to learn more about Vue, Nuxt, JavaScript or other useful technologies, checkout VueSchool by clicking this link or by clicking the image below:
It covers most important concepts while building modern Vue or Nuxt applications that can help you in your daily work or side projects 😉
✅ Summary
Well done! You have just learned how to build a recursive Vue component.
Take care and see you next time!
And happy coding as always 🖥️
Top comments (1)
I am playing with similar idea of having some strong fundament to build atop of it. I just want to make it as a mix of "opinionated" and "optionated" - some parts should be unified based on my best experience while additional modules (like Nuxt UI, FormKit or Supabase) should be turned on/off on demand.
I recently found a way how to pass a dynamic set of modules into nuxt.config.ts based on env values. It is still WIP, but in case anyone interested, here is the repo: github.com/AloisSeckar/nuxt-stack
My current idea is to publish it as a package and use as a base layer to extend from.
I didn't elaborate on testing yet. I have some setups on different projects, but I guess I will try to inspire in your solution too :)