TL;DR

Update the revalidateTag function calls to always include the profile parameter, as it is not optional despite the documentation suggesting it is.

Guidance

• Review the 150 instances of revalidateTag in the codebase to ensure profile is provided for each call.
• Verify the type definition in revalidate.d.ts to confirm that profile is indeed a required parameter.
• Consider reaching out to the Next.js documentation team to correct the documentation to reflect that profile is not optional.
• If possible, explore adding a default value for the profile parameter or making it optional in a future version of the revalidateTag function.

Example

No code snippet is provided as the issue is related to documentation and type definitions rather than a specific code implementation.

Notes

The fix involves updating existing code to comply with the actual requirement of the revalidateTag function, which may require significant changes if the function is widely used.

Recommendation

Apply workaround: Update all revalidateTag function calls to include the profile parameter, as this is the current requirement despite the documentation error.