Open purfectliterature opened 4 months ago
Any updates on this?
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
Link to the code that reproduces this issue
https://codesandbox.io/p/github/purfectliterature/typeerror-starter/master?import=true
https://github.com/purfectliterature/typeerror-starter
To Reproduce
npm run dev
.Error: operation(...) is not a function
when clearly it should have been an async function.Current vs. Expected behavior
Expected behaviour is for
createUser
to actually be compiled as an async function with a hybrid type. Not an empty object{}
.This wasn't the case and everything was fine up till next@14.1.0. Since next@14.1.1, I get this error. In the reproduction CodeSandbox, try running
npm i next@14.1.0; npm run dev
to see the app working fine.If you prefer to run it locally, you can clone the repository here: https://github.com/purfectliterature/typeerror-starter.
Provide environment information
Which area(s) are affected? (Select all that apply)
Output (export/standalone), Runtime, SWC, Webpack
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
It was fine up till next@14.1.0 and it breaks in next@14.1.1.
Potentially related to https://github.com/vercel/next.js/issues/62953 (?) [I posted there!] but that was closed and my use case is still erroring even in the latest release of Next.js at next@14.2.4.
Please refer to my README.md for more information about the error, how to reproduce, and some more context about my use case. It's not that long and very concise!