-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Watch-mode running too often when turborepo is set up inside a folder #8932
Comments
Hey, thanks for the issue. Any chance you can send over your daemon logs? You should be able to see them with |
Sure thing!
And the watch mode logs
|
Thanks! Just checking, is your |
Yes it is ignored, but like I wrote in the description, turbo repo is set up inside a folder called |
Ah gotcha. Would it be possible to add a nested |
As a workaround, sure. But I think this is not an all too uncommon use case. We have a monorepo with backend and frontend, the backend is in golang, and the frontend apps in JS, so we keep them separate. Would be cool if Turbo could move up the tree to find the closest gitignore file |
I'm also seeing e.g.
|
Verify canary release
Link to code that reproduces this issue
https://github.com/MattisAbrahamsson/turbo-repro
What package manager are you using / does the bug impact?
Yarn v2/v3/v4 (node_modules linker only)
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
2.0.12-canary.0
Describe the Bug
When having turbo setup inside a folder, and not in the root of the Github repository, turbo watch will run too often.
It's running every second or so, even though no files are changed. The script that runs have no side effects that would cause itself to re-run.
If everything is moved from the folder to the root of the repository turbo will work as expected.
Expected Behavior
I expect that turbo watch will not rerun every second as no source files have been changed.
To Reproduce
cd frontend
yarn install
yarn dev
Additional context
No response
The text was updated successfully, but these errors were encountered: