This is a DOM loading problem, introduces Echarts because when DOM is not loaded, an error will be reported when option gets the element and init starts to get it. The solution can be tried:
Read More:
- Vue Error: initialize failed: invalid dom [How to Solve]
- The echots in Vue reports an error. After obtaining the DOM element, the chart can be displayed. The console still reports an error
- Vue introduces ecarts, init initializes and reports an error
- The uni app references the vant component and reports an error unclosed bracket when compiling
- Vue3. X reports an error using vantui. Failed to resolve component: Van-**-**
- The Vue parent component uses ref to call the sub component method and reports an error
- Junit4 unit test reports an error invalid project specified
- Vue + TS reports an error after configuring the path alias
- Vue reports an error sasserror: expected newline
- Vue Alain startup command yarn serve reports an error
- Vue console reports an error duplicate keys detected: ‘XXXX’. This may cause an update error. Solution
- Vue install reports an error operation not allowed
- Vue router click the menu bar and the same module reports an error Vue router.esm.js? 2215:2065 Uncaught (in promise) Error
- Vue agent reports an Error 404 nginx configuration method
- [Solved] Echarts Error: There is a chart instance already initialized on the dom!
- [actual record of Android stepping on the pit] Android studio reports an error invalid gradle JDK configuration found after importing the project
- Hadoop reports an error. Cannot access scala.serializable and python MapReduce reports an error
- Vue project reports an error on ie11 white screen. Script1002: syntax error
- Vue introduction path is correct, but it always reports an error: already included file name‘ ××ב differs from file name ‘ ××ב only in casing.
- Vue executes NPM run Dev and reports an error: missing script: dev