Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
beta DIM throwing a SyntaxError on load
See original GitHub issueDIM Version
hasn’t loaded can’t see version
Browser Details
Firefox 95.0.2 (64-bit)
OS Details
macOS Monterey
Describe the bug
when visiting beta.destinyitemmanager.com this error shows up in the console:
Uncaught SyntaxError: identifier starts immediately after numeric literal main-3cb9b5.js:1:569356
This started about 30 minutes ago.
Logs
Uncaught SyntaxError: identifier starts immediately after numeric literal
main-3cb9b5.js:1:569356
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Syntax error from rjags - Stack Overflow
I'm trying to fit a hierarchical model with rjags for the first time; it looks pretty simple on paper, but I'm getting an...
Read more >Dim not loading : r/DestinyItemManager - Reddit
I'm on the PS5 and I downloaded the DIM app on my phone and when I try to use the app it's just...
Read more >Full Stack Error Handling with GraphQL and Apollo
networkError : Errors that are thrown outside of your resolvers. If networkError is present in your response, it means your entire query was ......
Read more >DIM Sync Error. Load failed. · Issue #8568 - GitHub
DIM tries to load over and over again. Only disabling DIM Sync and reenabling stops things, but the error persists. Another symptom is...
Read more >How to Fix Invalid SyntaxError in Python - Rollbar
The Python SyntaxError occurs when the interpreter encounters invalid syntax in code. Learn how to fix it.
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 Free
Top 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
Thanks, it makes sense but beta has been fixed, at this point the issue is some local cache you’ve got.
At this point this isn’t a massive breaking bug, but it is behavior that wasn’t there before so I am continuing to report.