Issue with Experimental PPR in Next.js 15 #74530
-
SummaryI’m running into an issue with my Next.js project. Initially, I was using Next.js 15, but when I encountered some problems, ChatGPT suggested installing the canary version. So, I installed the latest canary version ([email protected]) using: npm install next@canary --legacy-peer-deps Additional informationnextjs-15@0.1.0 predev
npm run typegen
nextjs-15@0.1.0 typegen
sanity schema extract --path=./sanity/extract.json && sanity typegen generate
✓ Extracted schema to ./sanity/extract.json
✓ Generated TypeScript types for 14 schema types and 0 GROQ queries in 0 files into: ./sanity/types.ts
nextjs-15@0.1.0 dev
next dev
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise /);
^
[CanaryOnlyError: The experimental feature "experimental.ppr" can only be enabled when using the latest canary version of Next.js.]
Node.js v20.14.0
// this is my next.config file:
import type { NextConfig } from "next";
const nextConfig: NextConfig = {
images: {
dangerouslyAllowSVG: true,
remotePatterns: [
{
protocol: "https",
hostname: "",
},
],
},
experimental: {
ppr: "incremental",
},
devIndicators: {
appIsrStatus: true,
buildActivity: true,
buildActivityPosition: "bottom-right",
},
};
export default nextConfig; ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I tested your repository and encountered the same issue. However, I was able to resolve it by installing the Canary version with the npm install next@canary --force Additional ConsiderationsKeep in mind that since PPR is an experimental feature, it may have bugs or instability issues. Use it cautiously, especially in production environments. For further details on using Partial Prerendering and other experimental features, refer to the official Next.js documentation. |
Beta Was this translation helpful? Give feedback.
I tested your repository and encountered the same issue. However, I was able to resolve it by installing the Canary version with the
--force
flag. Here's the command I used:Additional Considerations
Keep in mind that since PPR is an experimental feature, it may have bugs or instability issues. Use it cautiously, especially in production environments.
For further details on using Partial Prerendering and other experimental features, refer to the official Next.js documentation.