Unable to build intentional Dirty AMP page

[ka2jun8]

What version of Next.js are you using?

12.0.7

What version of Node.js are you using?

14.16.0

What browser are you using?

Chrome, Safari

What operating system are you using?

macOS

How are you deploying your application?

next

Describe the Bug

The following fixes have been made in 12.0.5.

#31505

This changed the warning to an error if the required components does not exist in _document.tsx.

Next.js supports AMP.
AMP also supports Invalid (dirty) AMP, like AMP Bento.

Even with Invalid AMP, we want to apply AMP validation and AMP optimization.

This could easily be achieved by changing Html to html.
This method is also introduced here (https://youtu.be/S_UttIYzKtM?t=736).

However, v12.0.5 causes an error.

Would you please take one of the following measures?

• Change error to warning (revert PR)
• Exclude Html from the target (

  next.js/packages/next/server/render.tsx

  Line 1311 in 9bcf678

  const expectedDocComponents = ['Main', 'Head', 'NextScript', 'Html']

  )
• Allows us to overwrite customized props for Html later (https://github.com/vercel/next.js/blob/canary/packages/next/pages/_document.tsx#L198)

Expected Behavior

It should be able to build the next project even if Html is html.

To Reproduce

To use html instead of Html in amp valid page (export const config = {amp: true}).

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.