Open alarbada opened 10 months ago
https://github.com/alarbada/reproduction-app
<div> <h1>hi</h1> </div>
/** Add your relevant code here for the issue to reproduce */ export default function Home() { return ( <div> h1>hi</h1> // <-- error! </div> ) }
Considerations: On page.tsx I'm using export const runtime = 'edge'. If you comment this line, the dev server works as expected.
export const runtime = 'edge'
I'd expect the dev server to pickup the jsx fix.
Operating System: Platform: linux Arch: x64 Version: #8 SMP PREEMPT_DYNAMIC Mon Nov 6 14:48:30 UTC 2023 Binaries: Node: 18.18.2 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.8.0 Relevant Packages: next: 14.0.3-canary.7 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: 5.1.3 Next.js Config: output: N/A
App Router
I've tested against next 13.5.4, next 14.0.0 / 14.0.2 and canary. All of them have the same error.
Facing the same issue in 14.0.4
Link to the code that reproduces this issue
https://github.com/alarbada/reproduction-app
To Reproduce
Considerations: On page.tsx I'm using
export const runtime = 'edge'
. If you comment this line, the dev server works as expected.Current vs. Expected behavior
I'd expect the dev server to pickup the jsx fix.
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router
Additional context
I've tested against next 13.5.4, next 14.0.0 / 14.0.2 and canary. All of them have the same error.