CSS is different in pages, vs local environment.
Below are previews for local vs pages renders.
SIf anyone has a response, please ping me when you reply.
CIs this on the custom domain? If so, there are a few zone settings that could be interfering:
https://developers.cloudflare.com/pages/platform/debugging-pages/#differences-between-pagesdev-and-custom-domains, like Auto Minify or Rocket loader
https://developers.cloudflare.com/pages/platform/debugging-pages/#differences-between-pagesdev-and-custom-domains, like Auto Minify or Rocket loader
When setting up your Pages project, you may encounter various errors that prevent you from successfully deploying your site. This guide gives an …
CIf it shows right on the pages.dev, then def one of those differences above
If it shows wrong on the pages.dev, sounds like an issue with the specific framework you are using, which would need more info
If it shows wrong on the pages.dev, sounds like an issue with the specific framework you are using, which would need more info
SShows incorrectly on pages domain as well.
SI'm currently using NextJS 13.4.4 with the
App directory.CCan you link the site/broken page?
I don't know too much about nextjs, might be something @5927 (a next-on-pages maintainer) could help with if they have a sec.
I would be curious if it works/deploys fine on Vercel but not CF Pages
I don't know too much about nextjs, might be something @5927 (a next-on-pages maintainer) could help with if they have a sec.
I would be curious if it works/deploys fine on Vercel but not CF Pages
SSI'll test on vercel really quickly
JThis is what I get on your site
Swhat on earth
JCould it be possible that your browser has cached old CSS? Try refreshing your browser cache
CLooks like minification is causing some of the asset hashes not to match on your custom domain as well
SI have even tried
SSUsing disable cache
SI assume this doesn't affect the html path?
SHow would one resolve this issue? Is it a local issue only?
CDisable minification on the custom domain via zone settings:
https://developers.cloudflare.com/pages/platform/debugging-pages/#differences-between-pagesdev-and-custom-domains
(log in to the Cloudflare dashboard
https://developers.cloudflare.com/pages/platform/debugging-pages/#differences-between-pagesdev-and-custom-domains
(log in to the Cloudflare dashboard
Speed > Optimization > Auto Minify
SAlrighty, did that.
SSeeing the changes now. Thank you for your time.
SNow, our of curiousity, how would one clear the brower's cache for the CSS items?
CClear? In settings
Bypass? Using that "Disable Cache" switch or Shift+F5
You're probably hitting edge cache though if it's on your Custom Domain, which you can disable via a Page Rule or a Cache Rule
Bypass? Using that "Disable Cache" switch or Shift+F5
You're probably hitting edge cache though if it's on your Custom Domain, which you can disable via a Page Rule or a Cache Rule
Sgotcha
SSo, when I make CSS changes to my website they won't update instantly won't they.. @chaika.me
SI have caching enabled on all things, to save me bandith and etc.
CPages doesn't recommend using edge cache in front of it. Internally it has its own cache, and you get unlimited static requests
SOH
STHAT NEATS
SAlrighty, now I got to figure out how to add it as an exception to the pages domain
JAnd for the actual static files (
/_next/static), we add a rule so that the function isn't invoked for them as well, so there should be no worries about them invoking the worker we generate in that departmentSWhy is this community sooo welcoming to nextjs vs the other options....
Ccan use Cache Rules pretty easily
Magic Link: https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules/new
Magic Link: https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules/new
SWould it be these caching options?
SJAlso fwiw, adding cache rules on top of Pages when using Next.js can also result in RSC payloads being cached instead of the HTML responses at the moment (Next.js are exploring workarounds for this), which is another reason to avoid it 
Cyea don't add one to force caching, just one to disable it for the default assets css/js/etc
SYou all are holding my hand
SIm not use to this, thank you so much!
S
SSo basically....
SI'm rebuilding my website to be more serverless and to work into a different CD/CI pipeline...
S
SThis is a first
iteration/mvp...Ssome people thought it was a final product, because of how functional/visually pleasing it was...
JHaha nice, wishing you all the best with it - you picked the perfect time since next-on-pages just hit v1 the other week 
SDo you know where I can read up on environment varibles?
SI'm trying to put my git hash in the build on page.
SAll of my versions always have a hash for reference.
