You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vercel/style-guide depends on eslint-plugin-tsdoc@^0.2.17. A new version, 0.3.0 is available but because "many authors treat a 0.x version as if the x were the major 'breaking-change' indicator" the new version, 0.3.0, does not satisfy the caret range constraint ^0.2.17.
When I update eslint-plugin-tsdoc in my project to 0.3.0 I get a runtime error when linting due to multiple versions of the plugin being available. @vercel/style-guide's dependency won't resolve to 0.3.0 and stays at 0.2.17. 😔
May we get a new version of @vercel/style-guide published with an update dependency on eslint-plugin-tsdoc? It could be ^0.3.0 but if a 0.4.x gets released it will be the same problem. I'm not sure if eslint-plugin-tsdoc intends to treat each minor version as a major version for now or not; if they don't plan breaking changes than 0.x could be used instead.
The text was updated successfully, but these errors were encountered:
@vercel/style-guide
depends oneslint-plugin-tsdoc@^0.2.17
. A new version,0.3.0
is available but because "many authors treat a0.x
version as if thex
were the major 'breaking-change' indicator" the new version,0.3.0
, does not satisfy the caret range constraint^0.2.17
.When I update
eslint-plugin-tsdoc
in my project to0.3.0
I get a runtime error when linting due to multiple versions of the plugin being available.@vercel/style-guide
's dependency won't resolve to0.3.0
and stays at0.2.17
. 😔May we get a new version of
@vercel/style-guide
published with an update dependency oneslint-plugin-tsdoc
? It could be^0.3.0
but if a0.4.x
gets released it will be the same problem. I'm not sure ifeslint-plugin-tsdoc
intends to treat each minor version as a major version for now or not; if they don't plan breaking changes than0.x
could be used instead.The text was updated successfully, but these errors were encountered: