20

On Chess Stack Exchange, there is a jQuery plugin which is integrated to display diagrams like this:

chess-replayer screenshot

Today (1 February 2022), at around the time when this chess question was first posted, the PGN Viewer plugin stopped working across the whole site. The issue seems to be reproducible on all devices and browsers.

Instead of the chess diagram, we now see a code block with the chess notation instead:

Question with chess diagram screenshot

There is a console error on all pages of the Chess SE and Chess SE Meta websites:

Console error

In We're Migrating our JavaScript, we were asked to post separate questions for bugs related to the JavaScript migration, so I am posting this question.

There is also a question about this on Chess Meta SE: Why has the PGN Viewer (replayer) stopped working?

Improve this question
20
  • 5
    That plugin was migrated a few weeks ago, so it sounds like something new broke that ended up affecting it. We'll take a look, thanks for the report!
    – Adam Lear StaffMod
    Feb 2, 2022 at 0:19
  • 1
    It is working for me right now (I didn't make any changes, just went to check it out). Can you reproduce the error? Extensions off? Browser and version?
    – Yaakov Ellis StaffMod
    Feb 2, 2022 at 8:02
  • 1
    @YaakovEllis Not working FF 96.3.0 for Android 10, nor FF 97.0 (64-bit) for Win11 Pro, nor Edge Version 97.0.1072.76 (Official build) (64-bit). Adblocker and extensions disabled.
    – Nick is tired
    Feb 2, 2022 at 8:48
  • Potentially worth noting I get different errors in each browser: justpaste.it/9jme9. Post used for testing: chess.stackexchange.com/questions/39117/…. Tested both signed in and signed out.
    – Nick is tired
    Feb 2, 2022 at 8:55
  • @AdamLear Was any fix done? For me, it's working on desktop now (Chrome, Edge, Firefox). It's not working on mobile (both browser and app), but that might have been an existing issue. I see some people saying that it does not work for them on desktop though.
    – hb20007
    Feb 2, 2022 at 10:00
  • @hb20007 FWIW, it is still not working for me in neither Edge nor FF.
    – Nick is tired
    Feb 2, 2022 at 11:03
  • It is working for me on all desktop browsers (tried on latest Chrome, Edge, FF). Not working for me on laterst Android Chrome.
    – Yaakov Ellis StaffMod
    Feb 2, 2022 at 11:30
  • 1
    @hb20007 Sure, I've just tried incognito on my work laptop, FF96.0.3 (64-bit) still has the same issue, as does Edge 97 and Chrome 98. Potentially region/ISP related?
    – Nick is tired
    Feb 2, 2022 at 13:38
  • 1
    Reproduced in FF 96.0.2 (64 bit) on Linux Mint
    – Zoe is on strike
    Feb 2, 2022 at 13:46
  • 1
    I can reproduce it (Chrome 97.0.4692.99 on Windows 11 Version 21H2 with incognito mode) when I use no VPN but it works with a VPN (or with some VPN locations) for me.
    – dan1st is crying
    Feb 2, 2022 at 14:01
  • 1
    @YaakovEllis FWIW, I was able to reproduce this last night before I status-reviewed. Chrome desktop on Win10.
    – Adam Lear StaffMod
    Feb 2, 2022 at 15:59
  • 1
    I think this could be due to a webpack bug, though I haven't been able to narrow it down to a minimal repro. I'm working on getting a workaround out the door, ETA some time in the next couple of hours. Apologies for the inconvenience, and thanks for reporting!
    – Benjamin Hodgson
    Feb 2, 2022 at 16:58
  • 1
    Looks like we're back up and running again. Thanks for the report!
    – Benjamin Hodgson
    Feb 2, 2022 at 18:40
  • 1
    @BenjaminHodgson (y) Looks good to me
    – Nick is tired
    Feb 2, 2022 at 18:46
  • 1
    I think it was a Webpack bug. The chess code is set up to be loaded dynamically by the Webpack runtime system, but it had also been configured as an (unused) entry point in the Webpack config. As far as I know that's meant to be supported, and I couldn't reproduce it when I ran the build on my machine, but removing the entry point for the chess code does seem to have fixed the issue.
    – Benjamin Hodgson
    Feb 2, 2022 at 19:31

1 Answer 1

Reset to default
10

This should be fixed now. I think it was a Webpack bug. The chess code is set up to be loaded dynamically by the Webpack runtime system, but it had also been configured as an (unused) entry point in the Webpack config. As far as I know that's meant to be supported, and I couldn't reproduce it when I ran the build on my machine, but removing the entry point for the chess code does seem to have fixed the issue.

Thank you again for reporting the bug!

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .