question-mark
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.

Console errors when clicking consumables "Error: [$parse:lexerr] Lexer Error: Unexpected next character at columns 33-33"

See original GitHub issue

It’s been a while since I’ve run DIM. I’m getting weird console messages when clicking consumables:

image

Here’s what I did-

This happens on both Mac and Windows. (Obviously I skipped the windows-build-tools step on Mac.)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
SunburnedGoosecommented, Mar 24, 2017

I work on both mac and pc. On Fri, Mar 24, 2017 at 10:49 AM Mulchman notifications@github.com wrote:

Same problem.

Would line endings have this kind of impact? That’s the only thing that might be different that I can think of.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/DestinyItemManager/DIM/issues/1546#issuecomment-289061388, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8GIO-zGvaq-4QtENNqDzcgYsSpPf2Vks5ro-X7gaJpZM4Mnorp .

0reactions
SunburnedGoosecommented, Mar 24, 2017

I was doing that with my exotic shards. I even moved the amount I chose. On Fri, Mar 24, 2017 at 11:09 AM Rob Jones notifications@github.com wrote:

happening on beta and stable you have to make the move popup appear with an amount selection to see the error though

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/DestinyItemManager/DIM/issues/1546#issuecomment-289067229, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8GIA7IHrbQECTcDAaXkLOkX5QloBjGks5ro-qygaJpZM4Mnorp .

Read more comments on GitHub >

github_iconTop Results From Across the Web

[$parse:lexerr] Lexer Error: Unexpected next character' on ...
I get the Lex error on the console but the regex works. Any idea how to get rid of the console error? –...
Read more >
[$parse:lexerr] Lexer Error: Unexpected next character at ...
I got this when I tested the wall. Steps: open firebug console start a wall for search term "Greferendum". firebug reports: Error: [$parse:lexerr]...
Read more >
63393 - An "Unexpected next character . . ." error occurs when ...
When a data grid includes a column name in Hebrew, an error message appears when both of these conditions are true: You expand...
Read more >
Error Reference: lexerr - AngularJS: API
Lexer Error : Unexpected next character at columns 0-0 [²] in expression [true]. Description. Occurs when an expression has a lexical error, for...
Read more >
[$parse:lexerr] Lexer Error: Unexpected next character' on ...
Error : [$parse:lexerr] Lexer Error: Unexpected next character at columns 0-0 [\] in ... http://errors.angularjs.org/1.2.6/$parse/lexerr?p0=Unexpected% ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found