question-mark
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.

[BUG] Error when generating docs (Parse error on line 33, Expecting 'CLOSE', got 'ID')

See original GitHub issue
Overview of the issue

When trying to generate the documentation, the following error occurs:

[11:17:26] Process page   : typealiases
[11:17:26] Process page   : enumerations
[11:17:26] Process page   : coverage
[11:17:26] Error: Parse error on line 33:
...      {{> menu data menu='normal' }}
-----------------------^
Expecting 'CLOSE', got 'ID'
Operating System, Node.js, npm, compodoc version(s)
  • Issue occuring with compodoc 1.0.0-beta.14 and compodoc 1.0.0-beta.15 (compodoc 1.0.0-beta.13 worked fine although the generation took forever)
  • Windows 7
  • NodeJS 8.2.1
  • Angular 4.3.2
Angular configuration, a package.json file in the root folder

The command we use:

compodoc src/lib --tsconfig src/tsconfig.docs.json

The referenced tsconfig file:

{
  "compilerOptions": {
    "baseUrl": "",
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [
      "es2016",
      "dom"
    ],
    "module": "es2015",
    "moduleResolution": "node",
    "outDir": "../out-tsc/app",
    "sourceMap": true,
    "target": "es6",
    "types": []
  },
  "exclude": [
    "test.ts",
    "polyfills.ts",
    "main.ts",
    "index.ts",
    "**/*.spec.ts",
    "app/**/*"
  ]
}
Compodoc installed globally or locally ?

locally

Motivation for or Use Case

The documentation won’t build at all.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
wshelleycommented, Oct 13, 2017

[11:07:53] Process page : variables [11:07:53] Process page : enumerations [11:07:53] Process page : coverage [11:07:53] Error: Parse error on line 33: … {{> menu data menu=‘normal’ }}
-----------------------^ Expecting ‘CLOSE’, got ‘ID’

0reactions
lock[bot]commented, Sep 30, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Parse Error in .hbs Template when Using Filters in Permalinks
Exception when trying to use a filter in the permalink front-matter in an .hbs template. In my example, I am generating multiple pages...
Read more >
Expecting 'ID', got 'NUMBER' - Stack Overflow
In handlebars, I am trying to access property 32 like following. <img src="{{ ICON.32 }}">. and I get following error. Module ...
Read more >
SyntaxError: JSON.parse: bad parsing - JavaScript | MDN
JSON.parse() parses a string as JSON. This string has to be valid JSON and will throw this error if incorrect syntax was encountered....
Read more >
Explanation of the error messages for the W3C Markup Validator
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty,...
Read more >
Bug listing with status RESOLVED with resolution FIXED as at ...
Bug :2 - "How do I attach an ebuild. ... Bug:146 - "imaging python lib ebuild error" status:RESOLVED resolution:FIXED severity:normal ... 1100+error lines!...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found