@BeatPlus moved your comment to a new issue: If your development environment is run in Windows, there is a bug in Nextjs path rendering. #4 fixes this