I create new next js project and I am facing this issue on next js default page
Answered
Transvaal lion posted this in #help-forum
Transvaal lionOP
Answered by Toyger
what is full path to your project, looks like this bug can happen with some inconsistent case in folder names in some shells.
42 Replies
Transvaal lionOP
Uncaught Error: Invariant: Missing ActionQueueContext
at useReducerWithReduxDevtoolsImpl
at useReducerWithReduxDevtoolsImpl
@Transvaal lion Uncaught Error: Invariant: Missing ActionQueueContext
at useReducerWithReduxDevtoolsImpl
seem like you are using
headers() or cookies() on client componentTransvaal lionOP
i nothng change from defult page after creating app by using npx create-next-app command
node version is 20.11.0
@Transvaal lion i nothng change from defult page after creating app by using npx create-next-app command
do you have redux devtools extension?
Transvaal lionOP
in chrome?
Transvaal lionOP
no
@Transvaal lion no
that's odd, maybe try it in incognito mode
Transvaal lionOP
yes check it incognito and also try it in edge
but it spnd my whole day
could you show the code?
Transvaal lionOP
sure
code is defult i never change any thing
both pages have default code
@Transvaal lion both pages have default code
what next verion?
Transvaal lionOP
{
"name": "app",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"react": "^18",
"react-dom": "^18",
"next": "14.1.0"
},
"devDependencies": {
"typescript": "^5",
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"autoprefixer": "^10.0.1",
"postcss": "^8",
"tailwindcss": "^3.3.0",
"eslint": "^8",
"eslint-config-next": "14.1.0"
}
}
"name": "app",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"react": "^18",
"react-dom": "^18",
"next": "14.1.0"
},
"devDependencies": {
"typescript": "^5",
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"autoprefixer": "^10.0.1",
"postcss": "^8",
"tailwindcss": "^3.3.0",
"eslint": "^8",
"eslint-config-next": "14.1.0"
}
}
maybe try
npm install --save next@14.0.4Transvaal lionOP
let me try
same
first page load perfectly then show error
@Transvaal lion same
what extension do you have in the browser?
look like its related to the extension
Transvaal lionOP
@Transvaal lion Click to see attachment
hmm could you disable all of the extension and see if it works?
Transvaal lionOP
i disable all but same
run
npx next infoTransvaal lionOP
npx next info
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 20.11.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.0.4
eslint-config-next: 14.1.0
react: 18.2.0
react-dom: 18.2.0
typescript: 5.3.3
Next.js Config:
output: N/A
warn - Latest canary version not detected, detected: "14.0.4", newest: "14.1.1-canary.7".
Please try the latest canary version (
Read more - https://nextjs.org/docs/messages/opening-an-issue
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 20.11.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.0.4
eslint-config-next: 14.1.0
react: 18.2.0
react-dom: 18.2.0
typescript: 5.3.3
Next.js Config:
output: N/A
warn - Latest canary version not detected, detected: "14.0.4", newest: "14.1.1-canary.7".
Please try the latest canary version (
npm install next@canary) to confirm the issue still exists before creating a new issue.Read more - https://nextjs.org/docs/messages/opening-an-issue
and try to return a div in home page
Transvaal lionOP
means back the page
@Transvaal lion means back the page
yes
return <div>home</div>Transvaal lionOP
same its show home as string on page after that show same error
Common carp
Tried running it through bash?
Transvaal lionOP
i am using power shell
let me start ubuntu in wsl
Toyger
what is full path to your project, looks like this bug can happen with some inconsistent case in folder names in some shells.
Answer
Transvaal lionOP
thanks now its working its all about path
my path is too long
now i short this and its working fine
thanks for your precious time
is next js declare any thing about path length or depth in documentatons