Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Typescript Complaint: Expected 0 type arguments, but got 1
See original GitHub issueHi,
I am using the nextjs-routes@0.1.0 with the withRoutes configuration but I am not sure it’s working as expected.
I am seeing the following error
I also cannot see the nextjs-routes nextjs-routes.d.ts types or any addition to my tsconfig.json.
Any ideas what am I missing?
Issue Analytics
- State:
- Created a year ago
- Comments:25 (16 by maintainers)
Top Results From Across the Web
Angular EventEmitter Error: Expected 0 type arguments, but ...
I am getting the type error, "Expected 0 type arguments, but got 1" despite following this tutorial to a T. https://youtu.be/I317BhehZKM?t= ...
Read more >Expected 0 arguments, but got 1 error in TypeScript | bobbyhadz
The error "Expected 0 arguments, but got 1" occurs when we pass an argument to a function that doesn't take any arguments. To...
Read more >Expected 0 type arguments, but got 1.ts(2558) after 6.2.6 update
What is the current behavior? After updating to the latest mongoose version 6.2.6 I get this error from typescript in my model. Expected...
Read more >4. Functions - Programming TypeScript [Book] - O'Reilly
TypeScript is smart enough to infer the parameter's type from its default ... sumVariadic ( 1 , 2 , 3 ) // Error...
Read more >EventEmitter Error: Expected 0 type arguments, but got 1
getting the following error EventEmitter Error: Expected 0 type arguments, but got 1 in Angular...emits the an event..throws error ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, I moved all the next and yarn stuff into the frontend folder and it works
We could consider resolving the pages directory relative to the the next.config.js instead of package.json, which isn’t a big lift after the deprecation of the cli invocation. I’m hesitant to make this a dedication configuration option, because we should be able to find routes identical to next. What do you think @MariaSolOs ?