Skip to content

Commit 25e7e72

Browse files
authored
docs: Add one more JS error message to the list
1 parent c974489 commit 25e7e72

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

troubleshooting/js-errors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ This page provides solutions for common JavaScript errors you may encounter whil
1616

1717
You may get runtime error messages in the browser console similar to the following:
1818

19+
* `Could not find 'TelerikBlazor.getLocationHost' ('TelerikBlazor' was undefined).`
1920
* `Microsoft.JSInterop.JSException: Could not find 'TelerikBlazor' in 'window'.`
2021
* `Error: Microsoft.JSInterop.JSException: Could not find 'initGrid' in 'window.TelerikBlazor'.`
2122
* `Error: Could not find 'TelerikBlazorPopup' in 'window'.`
@@ -63,7 +64,6 @@ Instead of this
6364

6465
````
6566

66-
6767
### TypeScript
6868

6969
By default, TypeScript results in compiled code that needs the `exports` object, and that is not available in Blazor by default, so it throws an error. A common workaround for that (defining an empty `exporst` object) causes errors from the Telerik JS Interop files. You can read more about the errors and the solutions in the [TypeScript Exports error breaks Telerik Blazor]({%slug common-kb-typescript-exports%}) KnowledgeBase article.

0 commit comments

Comments
 (0)