Next Dev for Turbo doesn't work
Answered
Chartreux posted this in #help-forum
ChartreuxOP
Hi, so I have seen the latest blog 14.2.3 that dev passed 99.8 test, meaning it's very stable by now, the thing is I am still unable to run my
The error itself not very clear on what's the problem.
Anyone has any clue on this?
I'm using PNPM, things I've tried:
- Removing pnpm-lock.yaml file and reinstall all modules
- Upgrading my PNPM version to latest
next dev --turbo even at this version, same error as 14.1.4:- invalid type: map, expected a boolean at line 206 column 29] {
code: 'GenericFailure'
}The error itself not very clear on what's the problem.
Anyone has any clue on this?
I'm using PNPM, things I've tried:
- Removing pnpm-lock.yaml file and reinstall all modules
- Upgrading my PNPM version to latest
9 Replies
@Chartreux Hi, so I have seen the latest blog 14.2.3 that dev passed 99.8 test, meaning it's very stable by now, the thing is I am still unable to run my `next dev --turbo` even at this version, same error as 14.1.4:
- invalid type: map, expected a boolean at line 206 column 29] {
code: 'GenericFailure'
}
The error itself not very clear on what's the problem.
Anyone has any clue on this?
I'm using PNPM, things I've tried:
- Removing pnpm-lock.yaml file and reinstall all modules
- Upgrading my PNPM version to latest
Well it passing 99.9% doesn’t mean it passing 100% :P yeah, it is still very very unstable and in this case it is a turbopack bug yes
Think of turbopack as the app router when it first came out
ChartreuxOP
Pretty unlucky I'm part of 0.2% 😄
I doubt you are part of that 0.2% though, it’s likely you are part of the bugs that the tests cannot catch
Having contributed to nextjs before, I have to say the test system is pretty messy and won’t catch like 70% of all bugs
That’s why you see many buggy releases, like the recent stable releases
ChartreuxOP
I see gotcha, it's fine actually I'm just wondering if there's solution.
Right, started to migrate app router when version 14 released because bad experience from users on version 13.
But it's good to get the detail about internal test system, thanks btw!
Right, started to migrate app router when version 14 released because bad experience from users on version 13.
But it's good to get the detail about internal test system, thanks btw!
Turbopack is unfortunately one of those black boxes that are very hard to configure and when it doesn’t work, it just doesn’t work no matter what you do
So yeah… use webpack
Answer