-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change prismjs to carat range? #33
Comments
Hi Karl! 👋 We have Prism as a dep for its core. Basically hidden internals. Loosening the range will cause stuff to break. I find preventing everything from exploding more important than older dependencies. Refractor also has a track record of updating fast after Prism updates, and if you use refractor itself with a loose range, you’ll also get Prism updates. The security vulnerability did not affect anyone using refractor, as we don’t support plugins. If there is an issue, it’s with Dependabot falsely claiming there was one 🤷♂️ |
Ok, understandable. Thanks for the answer :) |
No problem, thanks for understanding! |
Hi @wooorm !
Maybe going forward, you would consider changing to a carat version range for
prismjs
?It would help a lot for projects stuck with older dependencies which have
refractor
as a transitive dep (especially when things like security vulnerabilities withprismjs
happen).Anyway, thanks for the consideration!
The text was updated successfully, but these errors were encountered: