There is a Bug in Microsoft Edge Sourcemap Handling

Question

There is a Bug in Microsoft Edge Sourcemap Handling

Anonymous

Edge appears to have a bug in some stack trace displays. In this example, the trace claims the bug in is in clsx, on a call to a function that clsx doesn't call.

Here's the stack trace:

The stack trace claims the bug is on a call to the ApolloGraphQL function storeWriter.writeToStore located in clsx at line 1, position 374. But clsx doesn't interact with ApolloGraphQL at all.

I confirmed this with the developer of clsx (12,286,286 weekly downloads). He adds this observation.

There’s no Array.forEach in clsx either.

...Definitely a sourcemap issue, as shown by the green arrow in your screenshot

The bug happens when my app runs an ApolloGraphQL function, but the stack trace (and it goes on about 5 times as long as the part of it shown in the screen shot) never points to a line in my own code.

My code runs without error in Chrome, Firefox, and Safari, so the existence of a bug at all may be due to an error in Edge rather than in my code.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

2 answers

Answer 1

Hi, I'm Elise, a fellow user like yourself and I'd be happy to help with your issue.

This forum is mainly for consumer issues, for this type of issue I would recommended posting in the Q&A or Technet forum, as this is the intended audience for these type of queries:

https://learn.microsoft.com/answers/

https://social.technet.microsoft.com/Forums/

Alternatively you can submit feedback on the issue using the feedback hub app, you can find this in the start menu.

Kind Regards,

Elise

Answer 2

Anonymous

Thanks! A copy has been posted to https://learn.microsoft.com/.

Share via

There is a Bug in Microsoft Edge Sourcemap Handling

2 answers