Outdated vendor packages #31851
Unanswered
brianteeman
asked this question in
General
Replies: 4 comments
-
@wilsonge any idea? Without checking all the vendor packages it is possible that there are other outdated packages |
Beta Was this translation helpful? Give feedback.
0 replies
-
We can enable something like dependabot to do automatic Pull Requests. But I think that's about it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh I assume you're talking about stuff beyond the |
Beta Was this translation helpful? Give feedback.
0 replies
-
I didn't know about that command - very interesting
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Today purely by chance I noticed that the skipto package we are using is outdated and that the current release has a lot more features etc. The reason that we didn't automatically get notified of the new release was because it jumped to v3 and the entry in our package.json said ^2.1.1
My understanding is that the entry is correct because we wouldn't want to automatically update to a new major version which probably has b/c issues. However how can we avoid this scenario happening again with this or other packages?
Is there a way to have npm notify you that there is a newer version even if it is excluded by the entry in package.json?
(I will be submitting a PR next week for the new version once I update the Joomla code that implements it to take advabtage of the new features etc)
Beta Was this translation helpful? Give feedback.
All reactions