Skip to content

61FINTECH/nuxt-best-practices

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 

Repository files navigation

Nuxt.js best practices in 61 Financial News

Foreword

As Nuxt.js's homepage says:

With Nuxt.js, your application will be optimized out of the box. We do our best to build performant applications by utilizing Vue.js and Node.js best practices. To squeeze every unnecessary bit out of your app Nuxt includes a bundle analyzer and lots of opportunities to fine-tune your app.

Which means Nuxt.js was born with best practices and well-tuned performance.

However, this doesn't mean you don't need any best practices or tips when using it. On the contrary, if you are proficient in optimization and always keep best practices in mind, you could build a more stunning SSR app with it.

The best practices mentioned above is not only in the realm of Nuxt.js, but also in Vue.js / JS & Node.js / CSS / Nginx / Cache (client & server) / Lazy loading / Transferred size / Security / SEO / UX / etc. The topic is too huge to elaborate here. That's why we always need to keep learning, absorbing the experience of others so that we could always be standing on the shoulders of giants. (By the way, don't forget to share your experience)

Make good use of Google could help you climb up speedily. For example, search nuxt best practices and you will get these great articles:

The following content might not repeat their tips. Maybe you should find some time to check them out.

Best practices & Tips

Self-contained directory structure

According to Vue.js Style Guide · Tightly coupled component names:


Avoid using a nuxt module if you'd like to use it everywhere

Let's take axios-module as an example.

Update / Upgrade Nuxt.js to a newer version

About

(Working on it) Non-official best practices for Nuxt.js development

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published