Broken example with-aphrodite and Suspense

[artem-malko]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:22 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: 8.5.1
    Relevant Packages:
      next: 13.4.11
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A

There is a code example in the pull request: #52981

Which example does this report relate to?

with-aphrodite

What browser are you using? (if relevant)

Chrome Version 114.0.5735.198

How are you deploying your application? (if relevant)

No response

Describe the Bug

Just try to run an example with-aphrodite from my pull-request #52981

You will see that error:

Error: Cannot automatically buffer without a document
    at injectGeneratedCSSOnce (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/aphrodite/lib/chunk-d8625444.js:1877:13)
    at injectStyleOnce (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/aphrodite/lib/chunk-d8625444.js:1909:3)
    at injectAndGetClassName (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/aphrodite/lib/chunk-d8625444.js:2038:3)
    at css (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/aphrodite/lib/chunk-d8625444.js:2222:14)
    at Comp (webpack-internal:///./pages/comp.js:23:66)
    at renderWithHooks (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
    at renderIndeterminateComponent (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5731:15)
    at renderElement (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5946:7)
    at renderLazyComponent (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5936:3)
    at renderElement (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6029:11)
    at renderNodeDestructiveImpl (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6104:11)
    at renderNodeDestructive (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6076:14)
    at retryTask (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6528:5)
    at performWork (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6576:7)
    at /Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5382:14
    at scheduleWork (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:77:3)
    at pingTask (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5381:5)
    at ping (/Users/a.malko/Work/lab/nextjs-fork/examples/with-aphrodite/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5413:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Looks like there are some problems with streams and aphrodite.

Expected Behavior

Everything is working)

To Reproduce

Try to run #52981
The example: with-aphrodite

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!