-
Notifications
You must be signed in to change notification settings - Fork 29.1k
docs: watchOptions.pollIntervalMs #80687
New issue
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
base: canary
Are you sure you want to change the base?
Conversation
docs/01-app/03-api-reference/05-config/01-next-config-js/watchOptions.mdx
Outdated
Show resolved
Hide resolved
|
||
const nextConfig: NextConfig = { | ||
watchOptions: { | ||
pollIntervalMs: 1000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the default value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's None
(rust pun) - The default behavior is to use the system file watcher. When that fails, users can pass the polling option.
In other words, as far as I understand this won't do anything.
const nextConfig: NextConfig = {
watchOptions: {}
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ForsakenHarmony could you confirm? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't ping me, I no longer work at vercel (and certainly don't remember details like that on a PR that's >6 months ago)
Moving this PR to draft, because something is not working correctly in the polling implementation. |
Closes: https://linear.app/vercel/issue/DOC-4798/document-turbopack-watchoptionspollintervalms
Fixes: #80665