Login
Weird debugging js library problem
EDIT: the problem was a different script had some kind of runtime error. I’m not a great front end dev, but from some quick googling, it looks like when an unhandled runtime error happens earlier in the script, it causes the rest of the script to not run? Anyway, changing the name of the library maybe changed the order in which they were aggregated. Such a bizarre thing.
This is the most bizarre bug I’ve ever seen.
I have a library that simply refuses to attach, even if I attach it, call it mytheme/slibrary
If I declare the library as a dependency of another library, and attach that library, it works just fine. But if I attach slibrary directly, nothing.
The bizarre thing is, if I change the library name to anything that does not begin with an s, it loads just fine. But if I change this library to anything that begins with an s, nothing.
I’ve cleared and disabled every cache I can. I’ve attached it through render arrays, preprocessing, and in the twig file. Nothing.
The only thing that works is changing the name to something that begins with a different letter, or declaring that library as a dependency on something else, and attaching the something else.
I am utterly perplexed. I’m not very good at deeply debugging the render pipeline, so I have no idea where I’d attach a breakpoint to step through things.
I guess I’ll change the name of the library, but i wish I knew what the hell was happening.
Things work fine when js aggregation is off; it’s only a problem with js aggregation on.
I also cannot replicate this on any other install of Drupal I have access to.
Any ideas for where to debug?
[link] [comments]
