# Odd Bug in Microsoft Edge?

**URL:** <https://community.apollographql.com/t/odd-bug-in-microsoft-edge/6580>\
**Category:** Other Apollo Topics\
**Created:** [August 10, 2023, 2:42pm UTC](https://community.apollographql.com/t/odd-bug-in-microsoft-edge/6580 "2023-08-10T14:42:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikr00001](https://avatars.discourse-cdn.com/v4/letter/v/f05b48/32.png) [@vikr00001](https://community.apollographql.com/u/vikr00001)\
**Post date:** [August 10, 2023, 2:42pm UTC](https://community.apollographql.com/t/odd-bug-in-microsoft-edge/6580/1 "2023-08-10T14:42:54Z")

</div>

My app has a bug that only appears in Microsoft Edge. It doesn’t show up in Chrome, Firefox, or Safari. The stack trace doesn’t touch anyplace in my own Javascript code. I can’t tell yet if it’s a bug in Edge, or in the way Edge interacts with an npm package called `clsx` that is a dependency of [mui.com](http://mui.com) components, or in the way Edge interacts with Apollo, or all three. Here’s what the stack trace looks like:

 ![Screenshot 2023-08-10 at 10.27.26 AM](https://us1.discourse-cdn.com/flex019/uploads/apollographql/original/2X/7/7927b4a2ae1a25bfef8a500c665253c58ecfd9f0.png)

The stack trace goes on about 5 times that long. It never touches my own Javascript code directly.

So, it may be a bug in Edge and have nothing to do with Apollo. It’s weird that the trace is pointing at `clsx.mjs`, which doesn’t interact with Apollo at all.

I’m just posting this here in case anyone notices anything similar.

---

<div class="post-metadata">

**Author:** ![vikr00001](https://avatars.discourse-cdn.com/v4/letter/v/f05b48/32.png) [@vikr00001](https://community.apollographql.com/u/vikr00001)\
**Post date:** [August 13, 2023, 1:29pm UTC](https://community.apollographql.com/t/odd-bug-in-microsoft-edge/6580/2 "2023-08-13T13:29:03Z")

</div>

It’s starting to look like a bug in Edge.

The stack trace I posted above, 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`. He adds this [observation](https://github.com/lukeed/clsx/issues/78).

> There’s no Array.forEach in clsx either.  
> …Definitely a sourcemap issue, as shown by the green arrow in your screenshot

I’ve reported it to MS on [their support page](https://answers.microsoft.com/en-us/microsoftedge/forum/msedge_crash-msedge_macos/there-is-a-bug-in-microsoft-edge-sourcemap/ba8024f9-a206-434b-a24e-e89be985593f).

---

<div class="post-metadata">

**Author:** ![Justin\_Gonzalez](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/justin_gonzalez/32/5359_2.png) [@Justin\_Gonzalez](https://community.apollographql.com/u/Justin_Gonzalez)\
**Post date:** [February 6, 2025, 8:48pm UTC](https://community.apollographql.com/t/odd-bug-in-microsoft-edge/6580/3 "2025-02-06T20:48:28Z")

</div>

Archived on February 6, 2025, 8:48pm UTC