Christopher
Christopher
@felixmosh, It seems to me that this issue has already been resolved #5143. Fixed in #5148. Do you think this question should be opened?
I'm closing issues because the problem has been solved. Thanks!
@jasonsaayman It looks like I forgot about the types during development. I can make the changes—just let me know
I've made the changes. Please let me know if you have any comments on the updates
Hi! I can confirm that this issue still exists and it only occurs with version `0.19.x`. There is no such problem in the stable version `0.18.3`. Tested on version: `0.19.0-canary.bc5bfff1`...
+1 What problems arise because of this: https://github.com/vercel/next.js/discussions/66593