We can use `next build` and `next export` but we can't use `next start` because there is no node env

We can use

next build

next build

next build

next build and

next export

next export

next export

next export but we can't use

next start

next start

next start

next start because there is no node env to run with CF Pages.

Do you know of a way to write content to disk and keep it there, after build? Or is CF Pages filesystem ephemeral like Heroku?

Thanks

alphaβiota | EkonaviOP•5/21/22, 3:38 PM

Also, anyone know the env URL & Port for fetching from functions during build? thanks

kian•5/21/22, 3:39 PM

next start

next start

will never work since Pages isn't made for you to start your own server anyways

Aalphaβiota | Ekonavi We can use `next build` and `next export` but we can't use `next start` because ...

kavinplays•5/21/22, 3:39 PM

i don't think that you understand how pages works, when you do next build and next export, you write content to kv and save it there

kian•5/21/22, 3:40 PM

Anything you do in the build process & write to your output folder will be available when deployed but not for you to fetch in any manner like fsfs

kavinplays•5/21/22, 3:40 PM

you can use functions to store content in kv i think

Kkavinplays i don't think that you understand how pages works, when you do next build and ne...

alphaβiota | EkonaviOP•5/21/22, 3:47 PM

interesting. so CF Pages is writing to KV by default? or is this something we have to do during the build?

Kkavinplays i don't think that you understand how pages works, when you do next build and ne...

alphaβiota | EkonaviOP•5/21/22, 3:48 PM

yeah, if I have the mental model wrong for how all this is supposed to work, no goody

kian•5/21/22, 3:49 PM

build command -> throws stuff to /output-folder/output-folder -> /output-folder/output-folder contents are deployed globally (KV)

kian•5/21/22, 3:49 PM

if present,

/functions

/functions

folder -> built into a Worker -> ditto, deployed

kian•5/21/22, 3:50 PM

vastly simplified but you get the idea

kian•5/21/22, 3:50 PM

there is no environment for your own 'server' as such - just Workers & KV

alphaβiota | EkonaviOP•5/21/22, 3:51 PM

so we can write to global output folder after build then?

kian•5/21/22, 3:51 PM

There is no 'folder' after the build process is done

kian•5/21/22, 3:51 PM

The KV is abstracted away from you

alphaβiota | EkonaviOP•5/21/22, 3:52 PM

ah ha, ok, abstracted away

kian•5/21/22, 3:52 PM

Any dynamic functionality you want after building your static assets has to be done with Functions

kian•5/21/22, 3:52 PM

so you could have your own KV, sure

kian•5/21/22, 3:52 PM

https://developers.cloudflare.com/pages/platform/functions/#kv-namespace

alphaβiota | EkonaviOP•5/21/22, 3:52 PM

client creates new URL, content at URL is stored in KV, Function retrieves that content to serve new page back to client

kian•5/21/22, 3:53 PM

If that's how you want your site to work, sure

kian•5/21/22, 3:53 PM

Functions are only required if you want dynamic content

kian•5/21/22, 3:53 PM

If you just have static pages and assets, the build process handles everything

kian•5/21/22, 3:53 PM

i.e your site has something where users can make their own blog posts - you could store that content in KV & have a function for your /posts/posts page that fetches them all & renders them

alphaβiota | EkonaviOP•5/21/22, 3:54 PM

yes, it is a dynamic site, and now I am at a junction, deciding if I keep with CF pages or try deploying to a different platform where

next start

next start

and ISR/SSR work out of the box

alphaβiota | EkonaviOP•5/21/22, 3:57 PM

thanks for the info, at a crossroads here.

One more question please. During the build, is there a way to access Functions?

next build

next build

can call getStaticProps during build, and I've got those queries in Functions right now, works fine in dev env using http://localhost:8788

kian•5/21/22, 3:58 PM

Functions are built in the build process so not that I am aware of - but I've also never used

next

next

in my life (or any JS framework really) so someone else might have a solution to that problem

Kkian Functions are built in the build process so not that I am aware of - but I've al...

alphaβiota | EkonaviOP•5/21/22, 3:59 PM

ok, thank you

Isaac McFadyen•5/21/22, 4:00 PM

There's not because at the point of the build the Functions don't yet exist.

kian•5/21/22, 4:00 PM

Your Functions folder is built into a Worker and then deployed alongside your Pages project in general - although I think some frameworks just turn it into a _worker.js_worker.js

Isaac McFadyen•5/21/22, 4:00 PM

What you can do is run some Javascript as part of your build step.

Kkian Your Functions folder is built into a Worker and then deployed alongside your Pa...

Isaac McFadyen•5/21/22, 4:01 PM

Yeah, SvelteKit does that. Next.JS isn't support yet though

IIsaac McFadyen There's not because at the point of the build the Functions don't yet exist.

alphaβiota | EkonaviOP•5/21/22, 4:02 PM

i see, i see, thanks for the insight

SakuraFC•5/22/22, 8:30 AM

I'd suggest maintaining at least one old version at all times to avoid such things. Also having a versioned API (if you have any) will eliminate these scenarios (in most cases).