Skip to content

docs(common):Add another reason for js error #2451

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 23, 2024
Merged

docs(common):Add another reason for js error #2451

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa96a10
docs(common):Add another framework reason for js error
NansiYancheva Oct 18, 2024
0aed742
update after review
NansiYancheva Oct 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions troubleshooting/js-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,7 @@ If you get such errors, the reason may be:

* [The `telerik-blazor.js` JS Interop file is missing or the URL is wrong](#missing-file)
* [The `defer` attribute causes the script to load and execute too late](#defer-attribute)
* [A required order of the HTML tags in the web page](#html-tags-order)
* [TypeScript `exports` workaround break Telerik Blazor](#typescript)
* [A result of a syntax error in old browser](#syntaxerror-unexpected-token)

Expand All @@ -57,6 +58,21 @@ Sometimes, the JS Interop file is referenced correctly and returns successfully,

One solution is to remove the `defer` attribute of the `<script>` tag that registers `telerik-blazor.js`. On the other hand, `defer` improves the performance of your app by loading the script asynchronously. That's why a better option is to [keep the `defer` attribute and start the client-side Blazor framework manually]({%slug getting-started/what-you-need%}#javascript-file).

### HTML Tags Order

You can get the error when the application is navigating from an interactive page. If this is the case, register the `telerik-blazor.js` after the `<base href="/" />` in the `<head>` of the web page:

<div class="skip-repl"></div>

```HTML
<head>
...
<base href="/" />
<script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js" defer></script>
...
</head>
```

### TypeScript

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 `exports` 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%}) Knowledge Base article.
Expand Down
Loading