Would normally tag Walshy but he's Out of Office 🙂
Would normally tag Walshy but he's Out of Office 
SThanks! Also do you know if it's still the case on pages functions if static asset requests consume functions? (I'm using SvelteKit, mixture of pre-rendered and dynamic pages)
IStill the case but by the time Functions go GA (general availability, out of beta basically) it will be fixed
SYeah thought that was the case, hopefully nevika can help as I might be able to launch this weekend 
WI'm not sure we have a timeline right now but ASAP
I
KNot yet, but it's planned i believe
CAgreed here! Even if a quick hack to allow paid accounts to have larger limits would be super helpful.
AAny ETA on being able to run
next start to gain ISR functionality in our Nextjs apps? Thanks
AIs there anyway to download a zip of a pages build? Not sure why some assets aren't serving 
want to look at the bundle that pages is using, because it's fine when I build locally.
want to look at the bundle that pages is using, because it's fine when I build locally.
Kdo you mean ssr? if so then you need to wait till next supports cf pages and not the other way around
AWe can use
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
next build and next export but we can't use 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
AAlso, anyone know the env URL & Port for fetching from functions during build? thanks
Knext start will never work since Pages isn't made for you to start your own server anywaysKi 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
KAnything 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
fsKyou can use functions to store content in kv i think
Ainteresting. so CF Pages is writing to KV by default? or is this something we have to do during the build?
Ayeah, if I have the mental model wrong for how all this is supposed to work, no goody
Kbuild command -> throws stuff to
/output-folder -> /output-folder contents are deployed globally (KV)Kif present,
/functions folder -> built into a Worker -> ditto, deployedKvastly simplified but you get the idea
Kthere is no environment for your own 'server' as such - just Workers & KV
Aso we can write to global output folder after build then?
KNo
KThere is no 'folder' after the build process is done
KThe KV is abstracted away from you
Aah ha, ok, abstracted away
KAny dynamic functionality you want after building your static assets has to be done with Functions
Kso you could have your own KV, sure
Aclient creates new URL, content at URL is stored in KV, Function retrieves that content to serve new page back to client
KIf that's how you want your site to work, sure
KFunctions are only required if you want dynamic content
KIf you just have static pages and assets, the build process handles everything
Ki.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 page that fetches them all & renders themAyes, 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 and ISR/SSR work out of the boxAthanks for the info, at a crossroads here.
One more question please. During the build, is there a way to access Functions?
One more question please. During the build, is there a way to access Functions?
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:8788KFunctions are built in the build process so not that I am aware of - but I've also never used
next in my life (or any JS framework really) so someone else might have a solution to that problem
Aok, thank you
IThere's not because at the point of the build the Functions don't yet exist.
KYour 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