>> When you run, for example, "npm run dev" it will start both the Nuxt service, on port "3000", as well as the Feathers service, on port "3030". This is to keep the actual Nuxt- and Feathers-application separated, to offer the choice to create a backend/API-side of your application.
> ##### **Feathers**
> ##### **Feathers JS**
>> In Feathers JS, by default, you can post new data to the server externally; by example, from [Postman](https://www.getpostman.com/). In this boilerplate, creation of new users, has been disabled from such services.
>> [- When you make changes to files inside the "src" folder (where Feathers JS lives), it will not automatically restart the server (like nodemon). I will look into a solution for this. -]
> ##### **Nuxt**
> ##### **NUXT JS**
>> In this boilerplate, I am using Vuex (Vue Store), but I have made kind of a custom "nuxtServerInit". Adding that function will make the site crash.
>> You can also not change the Nuxt application's mode from "SPA" to "Universal" in this boilerplate. This will cause the store mutation "INIT_STORE" to not function, as well as authentication middlewares (Nuxt middlewares) to stop working. You are however free to try to find a different solution, that let's whomever to use either "SPA" or "Universal".
>> [- Major adjustments/changes to the "nuxt.config.js" file sometimes make the application crash. I have yet to find the source of this. Just restart the server whenever this happens. -]
