Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'initialize' of undefined #70

Closed
RobertHue opened this issue Nov 4, 2020 · 2 comments
Closed

Cannot read property 'initialize' of undefined #70

RobertHue opened this issue Nov 4, 2020 · 2 comments

Comments

@RobertHue
Copy link

Hello! I'm experiencing the following issue:

(etf) rhuemmer@PCAED685:~/etf$ ./node_modules/.bin/mmdc -i ./doc/sphinx/source/hardware/linux/tcp_client.mmd -o test.png -p ./doc/sphinx/source/puppeteer-config.json 
/home/rhuemmer/etf/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read property 'initialize' of undefined
    at __puppeteer_evaluation_script__:3:20
    at ExecutionContext._evaluateInternal (/home/rhuemmer/etf/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async ExecutionContext.evaluate (/home/rhuemmer/etf/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:106:16)
    at async ElementHandle.evaluate (/home/rhuemmer/etf/node_modules/puppeteer/lib/cjs/puppeteer/common/JSHandle.js:102:16)
    at async ElementHandle.$eval (/home/rhuemmer/etf/node_modules/puppeteer/lib/cjs/puppeteer/common/JSHandle.js:650:24)
(etf) rhuemmer@PCAED685:~/etf$

Puppeteer und mermaid.cli are the latest version:

(etf) rhuemmer@PCAED685:~/etf$ npm list --depth=1
etf@ /home/rhuemmer/etf
├─┬ @mermaid-js/mermaid-cli@8.8.2-beta.8
│ ├── chalk@4.1.0
│ ├── commander@6.2.0
│ └── puppeteer@5.4.1
├─┬ bufferutil@4.0.2
│ └── node-gyp-build@4.2.3
├─┬ chromium@3.0.2
│ ├── cachedir@2.3.0
│ ├── debug@4.2.0
│ ├── extract-zip@1.7.0
│ ├── got@11.8.0
│ ├── progress@2.0.3
│ ├── rimraf@2.7.1
│ ├── tmp@0.0.33
│ └── tunnel@0.0.6
└─┬ utf-8-validate@5.0.3
  └── node-gyp-build@4.2.3 deduped

Version of node and nodejs:

(etf) rhuemmer@PCAED685:~/etf$ nodejs -v
v8.10.0
(etf) rhuemmer@PCAED685:~/etf$ node -v
v15.0.1

This issue is related to: mermaid-js/mermaid#662
What could be the problem?

@MindaugasLaganeckas
Copy link
Member

@RobertHue : mermaid-cli is a thin layer over mermaid library. If there is already an issue filed against mermaid library, than I would suggest to wait until it is fixed there. There is not much we do in mermaid-cli.

@RobertHue
Copy link
Author

@MindaugasLaganeckas oh ok. Thank you very much.

I created the following Issue > Question on the mermaid library repository: mermaid-js/mermaid#1761.

So closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants