Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

V3 seems to have removed @import capability

See original GitHub issue

Hi, @ankit

I use github to manage a CSS file so versions can be monitored.

I use @import to view that stylesheet with Stylebot, and allow other users to automatically get updates, rather than have to copy and paste the CSS every time I update it.

@import has stopped working 😢
but also the stylesheet doesn’t update without removing and re-installing the Chrome extension.

(As I’ve Sponsored, I really hope you can keep the @import feature or re-enable it)

Thank you.

Issue Analytics

State:
Created 3 years ago
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

easawcommented, Aug 8, 2020

After testing this comes through very quickly now (even when using github raw - but with the full .css file extension).

So thank you very much, really appreciate your work! 😊👍

1reaction

ankitcommented, Aug 7, 2020

Thanks @easaw for the encouraging words.

For the caching issue, I will continue to investigate it further.

Until I have a fix for that, one workaround I suggest (instead of re-installing the extension) is to version your external css i.e. whenever you update your external css, update the filename and update your custom css in stylebot to point to the new version.

if you are using github, i have also noticed that urls like https://gist.githubusercontent.com/ankit/73bad5f20b389c08ea2a44e30338d4cf/raw take a while to actually get updated.