Configuration file for Pages projects does not support "alias" - Or can It? Using the new 2024-09-23 compat

[superjose]

Hi everyone 🤗

First, thank you, and excellent work with the new compatibility node release!!!

Things have VASTLY improved!

It just came right in time, as just last week, I was in the process of ditching Cloudflare altogether because many of my packages were breaking (and I even rearchitected the app to avoid this... But it wasn't possible in the end)

I'm having a last hiccup.

I'm trying to polyfill playwright-core from my configuration. I don't need the package because I won't use it from Cloudflare, but I can't remove the dependency directly as it's from a shared package in a mono repo structure.

Stack:

• TypeScript
• Remix V 2.12
• Vite
• Turborepo
• Wrangler 3.78.12

I tried the following:

name = "deploud"
compatibility_date = "2024-09-23"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = "./build/client"

[alias]
"playwright-core" = "./cloudflare-polyfills/playwright.js"

But I get an error back saying: Configuration file for Pages projects does not support "alias"

 - Configuration file for Pages projects does not support "alias"
    at readConfig (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/wrangler/src/config/index.ts:146:10)
    at getPlatformProxy (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/wrangler/src/api/integrations/platform/index.ts:104:20)
    at configureServer (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected][email protected]_typ_coyeyavnd3odz3uxb655lymsqa/node_modules/@remix-run/dev/dist/vite/cloudflare-proxy-plugin.js:55:17)
    at _createServer (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-CUvs3bbV.js:63019:20)
    at async configResolved (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected][email protected]_typ_coyeyavnd3odz3uxb655lymsqa/node_modules/@remix-run/dev/dist/vite/plugin.js:748:27)
    at async Promise.all (index 2)
    at Module.resolveConfig (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-CUvs3bbV.js:66343:3)
    at async Object.resolveViteConfig (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected][email protected]_typ_coyeyavnd3odz3uxb655lymsqa/node_modules/@remix-run/dev/dist/vite/plugin.js:72:20)
    at async build (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected][email protected]_typ_coyeyavnd3odz3uxb655lymsqa/node_modules/@remix-run/dev/dist/vite/build.js:192:20)
    at async Object.viteBuild (/Users/joseasilis/Documents/programming/alertdown/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected][email protected]_typ_coyeyavnd3odz3uxb655lymsqa/node_modules/@remix-run/dev/dist/cli/commands.js:183:5)

Any ideas?

[oxcabe]

I'm having a related issue, trying to polyfill node-fetch by using the approach presented in
Cloudflare Blog post 1 causes Wrangler to complain with:

- Configuration file for Pages projects does not support "alias"

Replacing pages_build_output_dir in favor of main causes the deployment to ignore the wrangler.toml file:

A wrangler.toml file was found but it does not appear to be valid. Did you mean to use wrangler.toml to configure Pages? If so, then make sure the file is valid and contains the `pages_build_output_dir` property. Skipping file and continuing.

This is the current state of my wrangler.toml:

#:schema node_modules/wrangler/config-schema.json
name = "redacted-dev"
pages_build_output_dir = "./build/client"
compatibility_date = "2024-11-18"

compatibility_flags = ["nodejs_compat_v2"]

[placement]
mode = "off"

[env.production.placement]
mode = "smart"

[alias]
"node-fetch" = "./utils/polyfills/fetch"

The blog post 1 also states the following:

Today, we are excited to announce a preview of improved Node.js compatibility for Workers and Pages.

To me, this implies that alias should work for both Pages and Workers.

[wongkristen]

@superjose @oxcabe Hey all! Did you guys ever figure out how use aliases in pages, or if Cloudflare even meant to support it? I'm trying to polyfill in as well and wondering if this is even the right approach. Getting the same error Configuration file for Pages projects does not support "alias"

[oxcabe]

AFAIK there's no way to use alias in Pages. What I ended up doing was to migrate the site from Pages to Workers...

If this is not a viable choice for you, there's the option to look for something like pnpm's overrides. Now, the polyfill would apply regardless of Wrangler being used or not. I had to do exactly this at some point, here's an issue where I describe the approach I came up with.

[sntran]

For those arrived here looking for a solution like me, it is currently said on Cloudflare documentation for Pages that:

Some functionality supported by Workers, such as module aliasing cannot yet be used by Cloudflare Pages projects."