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
As of the latest release, we've unpinned version dependencies.
This gives users more flexibility, and makes it easier to bump dependencies of this package (like @typescript-eslint) to support new TypeScript versions, etc.
This also introduces the risk of a plugin releasing a change to a recommended config in a minor release, which would be breaking as code that previously passed may now fail. Worse, a rule could be broken/removed in a minor release, breaking the config. We feel these risks are very low, which is why we opted to shelve this work for future.
The text was updated successfully, but these errors were encountered:
This is probably more urgent now as more typescript-eslint seems to be shipping changes to these configs in minor updates, example: typescript-eslint/typescript-eslint#8011
As of the latest release, we've unpinned version dependencies.
This gives users more flexibility, and makes it easier to bump dependencies of this package (like
@typescript-eslint
) to support new TypeScript versions, etc.This also introduces the risk of a plugin releasing a change to a recommended config in a minor release, which would be breaking as code that previously passed may now fail. Worse, a rule could be broken/removed in a minor release, breaking the config. We feel these risks are very low, which is why we opted to shelve this work for future.
The text was updated successfully, but these errors were encountered: