'Tailwind custom breakpoints override looks correct but Chrome DevTools shows default breakpoint

I've come across a strange occurrence and was wondering if anyone else has seen this. I'm using Tailwind and normally I have no issues changing my breakpoints, but this time when I override them as per the documentation spec, although the code does change, Chrome DevTools still shows the default breakpoint like in this picture here. Can't check in FireFox since they don't have the same visualization that chrome does. I'm really confused as to why it would do this. Anyone seen this before?

The style tab in DevTools shows correct code, it's just the visualization doesn't match what the code or style tab says. I'm starting to think it's a bug in Chrome or something.

For what it's worth, I'm in a custom webpack/Tailwind configuration with React, and maybe that has something to do with it but I don't know why or how that would be related when everything else works normally.

Chrome

Chrome

Config

Config



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source