search

vercel / turborepo

Build system optimized for JavaScript and TypeScript, written in Rust
https://turbo.build/repo/docs
MIT License
26.21k stars 1.81k forks source link

2.0.10+ doesn't keep the dev command open #8915

Closed hrishikesh-k closed 2 months ago

hrishikesh-k commented 2 months ago

Verify canary release

Link to code that reproduces this issue

https://github.com/hrishikesh-k/blog

What package manager are you using / does the bug impact?

npm

What operating system are you using?

Linux

Which canary version will you have in your reproduction?

2.0.12-canary.0

Describe the Bug

Running npm run dev starts my dev server but also immediately shuts it down. Here's the output from the terminal:

npm run dev

> dev
> turbo run @hrishikeshk/site#dev --no-cache

turbo 2.0.10

• Packages in scope: //, @hrishikeshk/adapter, @hrishikeshk/cache, @hrishikeshk/site, @hrishikeshk/utils
• Running @hrishikeshk/site#dev in 5 packages
• Remote caching disabled
@hrishikeshk/utils:build: cache miss, executing a1971776d99e9ef9
@hrishikeshk/utils:build:
@hrishikeshk/utils:build: 
@hrishikeshk/utils:build: > @hrishikeshk/utils@0.0.1 build
@hrishikeshk/utils:build: > tsc
@hrishikeshk/utils:build:

@hrishikeshk/adapter:build: cache miss, executing b1d849e4ddb8df85
@hrishikeshk/adapter:build:
@hrishikeshk/adapter:build: 
@hrishikeshk/adapter:build: > @hrishikeshk/adapter@0.0.1 build
@hrishikeshk/adapter:build: > tsc
@hrishikeshk/adapter:build:

@hrishikeshk/site:dev: cache miss, executing 9a82d2de968055b7
@hrishikeshk/site:dev:
@hrishikeshk/site:dev: 
@hrishikeshk/site:dev: > @hrishikeshk/site@0.0.1 dev
@hrishikeshk/site:dev: > vite dev
@hrishikeshk/site:dev:

@hrishikeshk/site:dev:   VITE v5.3.5  ready in 1273 ms
@hrishikeshk/site:dev:
@hrishikeshk/site:dev:   ➜  Local:   http://localhost:5173/
@hrishikeshk/site:dev:   ➜  Network: use --host to expose
@hrishikeshk/site:dev:   ➜  press h + enter to show help

 Tasks:    3 successful, 3 total
Cached:    0 cached, 3 total
  Time:    5.192s

Expected Behavior

The dev server should remain on.

To Reproduce

Run npm i (after changing the turbo version to anything after 2.0.9 in the root package.json) and npm run dev in the reproduction repo.

Additional context

Worked fine till 2.0.9. Broke in 2.0.10 and still broken in 2.0.11.

chris-olszewski commented 2 months ago

Your dev task needs to be declared as persistent.

Please reopen if this doesn't resolve your issue.