@@ -46,4 +46,4 @@ following behavior while you are doing development.
- When you run `next build` then `next start`, assuming you set externally the environmental variable STAGING to anything but 1, you will get the results assuming `isProd` is true.
- When your run `next build` or `npm run build` in production, if the environmental variable `STAGING` is set to `1`, `isStaging` will be set and you will get those values returned.
You can read more about this feature in thie blog post <ahref="https://vercel.com/blog/next5-1"target="_blank">Next.js 5.1: Faster Page Resolution, Environment Config and More</a> (under Environment Config).
You can read more about this feature in this blog post <ahref="https://vercel.com/blog/next5-1"target="_blank">Next.js 5.1: Faster Page Resolution, Environment Config and More</a> (under Environment Config).
@@ -54,7 +54,7 @@ Then you can create components and pages in `.tsx` or `.ts`
## Good to know
-[`firebase.json`](firebase.json:#L7) outlines the catchall rewrite rule for our Cloud Function.
- The empty `public/.gitignore` file is to ensure `public/` dir exists as it is required for Firebase Hosting. It is [configured](firebase.json:#L4)(by[default](https://firebase.google.com/docs/hosting/full-config#ignore)) that dotfiles (`public/.*`) are ignored from bein publicly served.
- The empty `public/.gitignore` file is to ensure `public/` dir exists as it is required for Firebase Hosting. It is [configured](firebase.json:#L4)(by[default](https://firebase.google.com/docs/hosting/full-config#ignore)) that dotfiles (`public/.*`) are ignored from being publicly served.
- The Cloud Function is named `nextjsFunc` (changeable in [firebaseFunctions.js](firebaseFunctions.js#L16) and [firebase.json](firebase.json#L8)).
-`public/*` files are statically served through [Firebase hosting](https://firebase.google.com/docs/hosting/full-config#public), not through [NextJs server](https://nextjs.org/docs/basic-features/static-file-serving).