-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
area: cliarea: devtriaged: bugIssue or PR has been reviewed by a maintainer and work is being trackedIssue or PR has been reviewed by a maintainer and work is being tracked
Description
Bug report
Suddenly after a couple weeks of development, my now dev command line doesn't work anymore. It started when I closed the terminal where it was running and opened a new one.
Now, it does the same even with a basic nextjs project

And even with the now init nextjs command line

To Reproduce
now init nextjs
cd nextjs
now dev
Expected behavior
The now dev server is properly launched and I can debug my code.
System information
- OS : macOS 10.14.6 - Memory: 16 GB
- Node : v10.16.0 (but tested with 8.x.x also)
- yarn 1.16.0 (but tested with 1.14 and 1.15 also)
- Version of Next.js: 9.0.5
Additional context
It happened to my collegues too. After a while, the command line just doesn't work anymore.
We have tried :
- Reinstall node, update node, downgrade node
- Reinstall yarn, update yarn, downgrade yarn
- Uninstall / Reinstall now
- rm -rf /Users/....../Library/Caches/co.zeit.now/
Nothing works. The command line throw the error directly after the yarn command, just like if it was a problem with the size of a file (maybe logs ?) or the number of arguments in a function?
Anyone can help ?
Thank you very much
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: cliarea: devtriaged: bugIssue or PR has been reviewed by a maintainer and work is being trackedIssue or PR has been reviewed by a maintainer and work is being tracked