Error parsing project
See original GitHub issueHi,
I’ve got the following issue :
Cannot parse your project. Make sure it's compatible with the Angular's AoT compiler. Error during parsing:
Users/xxxxxx/front-end/src/app/core/core.routing.ts(11,5): Error during template compile of 'CoreRoutingModule'
Reference to a local (non-exported) symbols are not supported in decorators but 'routes' was referenced
Consider exporting 'routes'.
But the AOT compilation is fine. We are using Angular 8.2. I’m using the latest version of ngrev available for OSX (0.0.27)
Here is tsconfig file and the core.routing file. (file renamed with txt extension for GitHub support)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
"There was an error parsing the specified project" : r/Reaper
This means that your file was completely erased and cannot be repaired. If you don't have any backups i'm afraid that your project...
Read more >REAPER Error: Parsing? - Cockos Incorporated Forums
I had just installed Reaper upgrade 1.22 before it occurred. It reads as a "REAPER Error... There was an error parsing the specified...
Read more >ERROR parsing project File: Content is not allowed in prolog
While no detail is provided, being unable to parse the project file indicates that it has corrupt information or special characters meddling with...
Read more >Setting up Cardano node: "cabal: Error parsing project file"
I get the following message: /cardano-node$ cabal new-build cabal: Error parsing project file ~/cardano-node/cabal.project:105: …
Read more >How to fix “Problem parsing the package error” in Android?
How to fix “Problem parsing the package error” in Android? · 1. You might have turned off “Allow installation from unknown resources” ·...
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
Requesting to provide solution for the issue. I am also getting same
I’ve just stumbled across this on a project we recently upgraded.
It looks to be where we have started
using the () => import('../app/')
syntax for lazy loading modules.