Typescript error when setting export const experimental_ppr = true;

[ryanknight09]

Summary

When enableing ppr in Next.js 15RC, the export const experimental_ppr = true; in a page.tsx or layout.tsx file is considered an error by typescript still.

"experimental_ppr" is not a valid Next.js entry export value.ts(71002)

Is there a fix to this or am I missing something? The feature works as expected and the builds come work just fine as well. The type error is just annoying in my layout file. Thanks for the insight.

Additional information

Next config:

`
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
ppr: 'incremental',
},
};

export default nextConfig;
`

Example

No response

[icyJoseph]

Hi,

I think the RC branch hasn't been updated for a while now.

I found this, merged to canary, PR:

• update typescript plugin to support experimental_ppr #66141

Which shows, that the issue you are facing has been fixed, in canary. My guess is that RC hasn't received these commits just yet.

I see in the TypeScript plugin code, that experimental_ppr, is indeed allowed.

Also, this comment, #70718 (comment), validates that the RC, hasn't been updated for some time.

[icyJoseph]

Aha, that's odd though 🤔 maybe that PR is not released into that canary (for v15)

[icyJoseph]

I see that the fix is still in the canary git branch:

• https://github.com/vercel/next.js/blob/canary/packages%2Fnext%2Fsrc%2Fserver%2Ftypescript%2Frules%2Fconfig.ts

API_DOCS has experimental_ppr and that is checked before emitting the TS error.

[adrianbravomr]

At the end, for me, it was IntelliCode VS Code Extension screwing things up. I've disabled it until i find a better alternative (And learn to perform a more efficient debugging).

Thanks for the support @icyJoseph

[ryanknight09]

Ah, thanks @icyJoseph.

[icyJoseph]

If this worked out for you, please don't forget to mark as answered 👍