@cloudflare/[email protected]
Hi! We released
@cloudflare/[email protected] earlier today which caught some people out — apologies if you were affected by the breaking change. We've tagged the latest 0.X release (@cloudflare/[email protected]) as latest again so that, if you are relying on the implicit npx @cloudflare/next-on-pages build command, you'll pull that version and hopefully will be back to a good state.
Going forward, we're going to migrate everyone who has an implicit npx @cloudflare/next-on-pages build command to npx @cloudflare/next-on-pages@pre-v1 . This will keep them on the 0.X releases. We'll, only then, point latest back at the 1.X releases. The framework preset in the dashboard will be updated to npx @cloudflare/next-on-pages@1 so new projects will be using the newer versions by default.
Apologies once again for the inconvenience and confusion. We're also going to be recommending you install @cloudflare/next-on-pages to your project dependencies so your builds are consistent and reproducible.5 Replies
cc @sathoro
yeah this is a good fix. I've added
@cloudflare/[email protected] to our package.json for now. will check out the new updates and upgrade later when it is more convenientShould hopefully be a trivial upgrade: bump to
@cloudflare/next-on-pages@^1.0.0 in your package.json and add nodejs_compat to your the compatibility flags on your Pages project settings page in the dashboard.can I get a Beta Tester role for using
next-on-pages in prod despite being told I should avoid it? 🤣 <a:doge_cool:691370185172582430>