Nuxt Toolbox Template
Build Setup
# install dependencies
$ npm install
# serve with hot reload at localhost:3000
$ npm run dev
# build for production and launch server
$ npm run build
$ npm run start
# generate static project
$ npm run generate
Redirects
In the netlify.toml
configuration file there is an example of how to implement redirects. Redirects can be used to do many things from redirecting Single Page Apps more predictably, redirecting based on country/language to leveraging On-Demand Builders for Distributed Persistant Rendering.
In the example we'll be using redirects to have a more simplified call to Netlify functions. Technically when you call a function you will be making a call to https://yoursite.netlify.com/.netlify/functions/functionName
. In order to make a cleaner path we'll redirect all calls from a path including /api
to call on the Netlify functions. So the path will be simplified to https://yoursite.netlify.com/api/functionName
, a lot easier to remember too.
Example
[[redirects]]
from = "/api/*"
to = "/.netlify/functions/:splat"
status = 200
force = true
First we create a section in the .toml
for the redirect using [[redirects]]
. Each redirect should have this line to start the redirect code, and the redirects will be executed in the order they appear in the .toml
from top to bottom.
The bare minimum needed is the from
and to
, letting the CDN know when a route is requested, the from
, forward it on to another path, the to
. In the example, we also added an 'Ok' status code, 200, and set the force
to true to make sure it always redirects from the from
path.
There are many ways to use redirects. Check out the resouces below to learn more.