We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
res.flushHeaders();
https://github.com/childrentime/nextjs-earlyhints
localhost:3000
current: don't have any response
expected: have the correct response
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:32:52 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T8122 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 20.12.0 npm: 10.5.0 Yarn: 1.22.21 pnpm: 8.15.5 Relevant Packages: next: 14.2.4 // Latest available version is detected (14.2.4). eslint-config-next: N/A react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A
Pages Router
next dev (local)
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Link to the code that reproduces this issue
https://github.com/childrentime/nextjs-earlyhints
To Reproduce
localhost:3000
Current vs. Expected behavior
current: don't have any response
expected: have the correct response
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:32:52 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T8122 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 20.12.0 npm: 10.5.0 Yarn: 1.22.21 pnpm: 8.15.5 Relevant Packages: next: 14.2.4 // Latest available version is detected (14.2.4). eslint-config-next: N/A react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Pages Router
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: