navigation.js:173 Uncaught TypeError
See original GitHub issueUpdated my packages today and started getting this error when i click a link on my webpage.
navigation.js:173 Uncaught TypeError: Cannot read property 'getElementsByTagName' of null
at navigation.js:173
170 | if (document.title) {
171 | pageName = document.title
172 | }
> 173 | const pageHeadings = document
174 | .getElementById(`gatsby-focus-wrapper`)
175 | .getElementsByTagName(`h1`)
176 | if (pageHeadings && pageHeadings.length) {
Issue Analytics
- State:
- Created 4 years ago
- Reactions:21
- Comments:26 (7 by maintainers)
Top Results From Across the Web
Uncaught TypeError: Cannot read property 'show' of undefined
When you create blocks you start from 1 for (let i = 1; i < blockCount; i++) { blocks.push(new Block(blockCol * 60 +...
Read more >Script Error thrown with CDN & Webpack Externals - Telerik
I decide to use webpack external to dynamically load the scipt files using CDN links. But, I am getting the below script error....
Read more >Uncaught TypeError: this._contentReadyAction is not a function
Hi there, I have an error "this.contentReadyAction is not a function" and have attached the console stack trace from it.
Read more >Protoype Error Loading Map - Esri Community
Using Webpack with Rails 5/StimulusJS to load a map in an application. webpack config: new ArcGISPlugin({ // exclude 3D modules from build
Read more >server error typeerror: cannot read properties of null (reading ...
Uncaught TypeError : Cannot read properties of null (reading 'useContext') ... Navigate to instance list; Click on a instance from the list ...
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
Fixed and published in
gatsby@2.19.12
Apologies for this.
Fix incoming