J
vercel CLI version), I've got a pet project deployed to Pages with next 15.0.3, app router, apis/middleware, etc and it's working greatJ
vercel CLI should fix it)
M
SSS
M
J
R
J
npm run pages:build && wrangler pages dev) similar to running the Next.js dev server in terms of speed? Right now it feels quite cumbersome in comparison to Next with turbopack or Vite because of 15+ second build times. Or is the OpenNext initiative looking to resolve this? By making then runtimes similar when using the Next.js dev server vs deployed on Pages?
Cprocess.env.CUSTOM_VAR cannot find my env, even though I added the secrets on Wrangler.
RJJ
setupDevPlatform is definitely helpful there. But sometimes I have to debug an issue due to the subtle differences between runtimes of next dev (Vercel Edge) and wrangler pages dev (workerd) because the latter is what runs on production. So I'm looking for a faster workflow to do that locally. Is the best option currently to run npx @cloudflare/next-on-pages --watch, and then re-run wrangler pages dev on changes to the build assets? I tried the --live-reload functionality of wrangler pages dev in this situation but it did not seem to trigger reloads of the browser page. And when I manually reload the page, it still referencing the JS chunk files from the original build in the page index HTML causing loading errors until I manually restart the Wrangler dev server. I haven't tried Nodemon yet to restart the Wrangler dev server on build changes, so that might be an option. I'm curious how other people are tackling this.
00
NJRBNCCNCN
NNN
--frozen-lockfile?00JJ
N
node:async_hooks inside of the custom entrypoint. However, it errors out:
DDN
SS
SRRNJSNC
env variable when my project is build on cloud flare. process.env.MY_VARIABLE is unable to work.
I tried to push my variables via wrangler, via the dashboard, everything. Do you have an idea ?vercelvercelIllegal invocation: function called with incorrect `this` referencenpm run pages:build && wrangler pages devprocess.env.CUSTOM_VARenvsetupDevPlatform next devwrangler pages devwrangler pages devwrangler pages devnpx @cloudflare/next-on-pages --watch--live-reload22:50:27.881 ▲ Its type '() => Promise<JSX.Element>' is not a valid JSX element type.
22:50:27.881 ▲ Type '() => Promise<JSX.Element>' is not assignable to type '(props: any, deprecatedLegacyContext?: any) => ReactNode'.
22:50:27.881 ▲ Type 'Promise<Element>' is not assignable to type 'ReactNode'.Ignoring not compatible lockfile at /opt/buildhome/repo/pnpm-lock.yaml--frozen-lockfilepnpm install --frozen-lockfile
ERR_PNPM_LOCKFILE_BREAKING_CHANGE Lockfile /path/to/proj/pnpm-lock.yaml not compatible with current pnpmAdding the packageManager field to our package.json fixed it, e.g.
"packageManager": "pnpm@9.12.2+sha256.2ef6e547b0b07d841d605240dce4d635677831148cd30f6d564b8f4f928f73d2",node:async_hooks✘ [ERROR] Could not resolve "node:async_hooks"
2 │ import { AsyncLocalStorage } from 'node:async_hooks';
╵ ~~~~~~~~~~~~~~~~~~
The package "node:async_hooks" wasn't found on the file system but is built into node. Are you
trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this
error.info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
23:13:35.716 ▲ Failed to compile.
23:13:35.717 ▲ ./src/app/[locale]/categorieen/[...id]/page.tsx:1:10
23:13:35.717 ▲ Type error: Module '"react"' has no exported member 'use'.
23:13:35.718 ▲
23:13:35.718 ▲ > 1 | import { use } from 'react';
23:13:35.718 ▲ | ^
23:13:35.718 ▲ 2 | import { and, eq, isNotNull } from 'drizzle-orm';
23:13:35.718 ▲ 3 | import { redirect } from '@/i18n/routing';
23:13:35.718 ▲ 4 | import { notFound } from 'next/navigation';
23:13:35.783 ▲ ELIFECYCLE Command failed with exit code 1.
23:13:35.823 ▲ Error: Command "pnpm run build" exited with 1env variableprocess.env.MY_VARIABLEwrangler
CDCloudflare Developers / general-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / pages-help