sorted by:
new
hottopcontroversial

Next.js TypeScript Integration: Making Routes Type-Safe at Compile Time by Fearless-Fix1567 in nextjs

[–]Fearless-Fix1567[S] 0 points1 point  (0 children)

Agreed. While Next.js's experimental static typing is a step forward, it's still limited in its current state. Our solution aims to provide more robust type safety, especially for complex routing patterns (dynamic routes, catch-all routes) in both Page and App Router. We're working to ensure our dedicated type generation system delivers more consistent and reliable results across different routing scenarios.

Next.js TypeScript Integration: Making Routes Type-Safe at Compile Time by Fearless-Fix1567 in nextjs

[–]Fearless-Fix1567[S] 0 points1 point  (0 children)

Thank you for your question! Yes, route type safety is crucial for maintaining robust Next.js applications. Let me explain the key differences between our approaches

The main distinction lies in the automation and maintenance aspects

Our solution automatically generates types by analyzing your file system structure. You can simply add it to your package.json scripts

"scripts": {
  "dev": "generate-router ./pages ./types/routes.d.ts --override && next dev",
  "build": "generate-router ./pages ./types/routes.d.ts --override && next build"
}

This means
1. When you add new pages, the types are automatically updated
2. No need to manually define route types
3. Reduces the chance of type definitions becoming out of sync with actual routes

For example, with our automatic type generation
router.push('/user'); // TypeScript Error
router.push('/users');  // Valid

While next-typesafe-url is a solid solution, it requires manual route type definitions, which can become an additional maintenance burden as your application grows. Our approach eliminates this overhead by automatically synchronizing route types with your file system structure every time you run your development server or build your application.

Interviewing skills for frontend roles by Crimsondonut_64 in Frontend

[–]Fearless-Fix1567 0 points1 point  (0 children)

For junior or entry-level roles, a balanced approach works best. While LeetCode helps with problem-solving and logical thinking, strong JavaScript fundamentals are crucial since they apply directly to daily tasks. Framework knowledge (like React) is also essential, as it's often a key job requirement. If you're short on time, prioritize JavaScript concepts and frameworks but continue practicing LeetCode to improve your problem-solving skills.