Problems with tamagui styles on Cloudflare pages about t4-app HOT 10 CLOSED

@darthwade This was originally set, it must have been removed by a recent PR.

I added it back so other people don't experience this. Thanks for debugging!

from t4-app.

Btw, during deployment I also encountered "Error: Could not access built-in Node.js modules. Please make sure that your Cloudflare Pages project has the 'nodejs_compat' compatibility flag set."

adding node_compat to wrangler.toml didn't help, but applying node_compat via CF dashboard helped

[env.preview]
name = "zeus-web-preview"
workers_dev = true
node_compat = true
compatibility_flags = [ "nodejs_compat" ]

[env.production]
name = "zeus-web"
route = "zeus-3v5.pages.dev/*"
workers_dev = false
node_compat = true
compatibility_flags = [ "nodejs_compat" ]

from t4-app.

Yep you have to set node_compat via the CF dashboard. I'm open to solutions that make that process programatic.

Do you have optimizeCSS set in next.config.js? Turn it off if you do.

from t4-app.

from t4-app.

That's strange. Ensure your fork is up to date with the main branch and re-deploy.

from t4-app.

will do, I created it yesterday via pnpm create t4-app, locally looks good

from t4-app.

Updated to latest version from main branch, so probably there's some problem during building or deployment/cf configuration
https://zeus-3v5.pages.dev

from t4-app.

Make sure your CF deployment is set to node 18!

from t4-app.

Strange, recreated cf project from scratch with NODE_VERSION 18 env var, but still same problem https://zeus-web.pages.dev

from t4-app.

After adding TAMAGUI_TARGET=web it finally works :)
@timothymiller thanks for help!

"dev": "TAMAGUI_TARGET=web pnpm with-env next dev",
"build": "TAMAGUI_TARGET=web pnpm with-env next build",
"start": "TAMAGUI_TARGET=web pnpm with-env next start",

from t4-app.