guess-parser doesn't work correctly with TypeScript 5
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I've recently updated dependencies in my monorepo, namely NX 16, Angular 16.1 and TypeScript 5.1. My app doesn't use standalone components yet and still relies on modules, but still `guess-parser` no longer works correctly. `parseAngularRoutes` results in an error about multiple root modules found. And when debugging I can see that the registry tree is not generated correctly.
When I downgrade my TypeScript to 4.9.5 it works fine.
Is support for TypeScript 5 planned? And are the standalone components for Angular going to be supported? It is a stable feature now.
Contributor guide
Research direction
Start with the parseAngularRoutes entry point and reproduce the registry-tree failure using TypeScript 5.1 with NX 16 and Angular 16.1, then compare it with TypeScript 4.9.5. Confirm that module-based applications no longer produce the multiple-root-modules error; separately determine whether standalone-component support is part of the accepted scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100