You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Avoid using third packages or complex configuration to achieve this
Track files that Next itself can't track
Non-Goals
I think it is very clear...
Background
I'm actually using a package called next-remote-watch that do the job for .mdx and .json files, the problem is that I can't use Turbopack with it and it is susceptible to break. besides, a native implementation it's gonna be more optimized and ready to use without installing packages and doing complex configuration for it.
Example:
Before:
"scripts": {
"dev": "next-remote-watch",
}
After:
"scripts": {
"dev": "next --watch .",
}
In the last example now you have the option to extend the configuration with the options that Next's CLI offers to you (like --turbo).
Proposal
Hmm, like a standard --watch option, like the one that has node, bun, etc...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-Goals
I think it is very clear...
Background
I'm actually using a package called
next-remote-watch
that do the job for.mdx
and.json
files, the problem is that I can't use Turbopack with it and it is susceptible to break. besides, a native implementation it's gonna be more optimized and ready to use without installing packages and doing complex configuration for it.Example:
Before:
After:
In the last example now you have the option to extend the configuration with the options that Next's CLI offers to you (like
--turbo
).Proposal
Hmm, like a standard
--watch
option, like the one that has node, bun, etc...Beta Was this translation helpful? Give feedback.
All reactions