Upgrading to v1.14: "TypeError: dashboardsTemplate is null"
See original GitHub issueHi William,
Here is that console output I spoke about at our meeting last week. We’re upgrading to v1.14 and are coming across this error. Nothing appears in the browser (ie, no toolbar, no navigator, no orange). It sounds like I need to register the dashboard. Sorry if I missed the announcement, but time is of the essence. Thanks,
-Chris
goog.require could not find: jspb.utils
Error: goog.require could not find: jspb.utils
goog.require could not find: jspb.utils
Error: goog.require could not find: jspb.Message
goog.require could not find: jspb.Message
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: export declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
SyntaxError: import declarations may only appear at top level of a module
TypeError: dashboardsTemplate is null
ready http:/
_readySelf http:/
_ready http:/
_tryReady http:/
_initFeatures http:/
__initialize http:/
createdCallback http:/
i http:/
n http:/
t http:/
n http:/
o http:/
t http:/
n http:/
n http:/
n http:/
t http:/
o http:/
t http:/
v http:/
i http:/
r http:/
w http:/
t http:/
<anonymous> http:/
n http:/
i http:/
t http:/
o http:/
r http:/
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
import declarations may only appear at top level of a module vue ...
tensorflow/tensorboardUpgrading to v1.14: "TypeError: dashboardsTemplate is ... of a module TypeError: dashboardsTemplate is null ready http:/ _readySelf ...
Read more >Jest causing "Cannot read properties of null (reading 'isCE ...
The promise rejected with the reason "TypeError: Cannot read properties of null (reading 'isCE')".] { code: 'ERR_UNHANDLED_REJECTION' }.
Read more >2021年08月_weixin_39602891的博客_CSDN博客
7月10日王者荣耀服务器维护,王者荣耀7月10日更新了什么王者荣耀7月10日更新内容...,虚拟服务器透传步骤,moxa串口服务器配置点对点透传模式步骤,新手云服务器系统, ...
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 FreeTop 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
Top GitHub Comments
This is a normal behavior. When you define a Polymer component, you specify what the DOM should look like in a template which by itself is not user visible element. Polymer, during the runtime, parses the template HTML to figure out its data bindings and hides the template content away from the user. It, after parsing it, does hold the reference to inner templates in the memory which gets used only when a Polymer component is created via
document.createElement
(or HTML).I was trying to describe the internals of Polymer one does not need to know about. I brought it up while trying to explain why the
template
was empty and why you were only seeingdocument-fragment
inside.