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
Is your feature request related to a problem? Please describe.
Currently, the repository’s .gitignore file excludes both yarn.lock and package-lock.json. Ignoring these lock files can lead to inconsistencies in dependency versions across different environments, which may cause compatibility issues.
Describe the solution you'd like
Please remove yarn.lock and package-lock.json from the .gitignore, allowing these files to be committed to the repository. This ensures everyone is using the same versions of dependencies for consistent, reproducible builds.
Describe alternatives you’ve considered
Relying on the hope that no dependency introduces breaking changes and that all maintainers adhere perfectly to semantic versioning. However, this is often unpredictable in practice and can result in compatibility issues.
Additional context
Lock files serve as a record of exact dependency versions. Including them in version control helps avoid unintentional mismatches and ensures consistent environments for all contributors.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the repository’s
.gitignore
file excludes bothyarn.lock
andpackage-lock.json
. Ignoring these lock files can lead to inconsistencies in dependency versions across different environments, which may cause compatibility issues.Describe the solution you'd like
Please remove
yarn.lock
andpackage-lock.json
from the.gitignore
, allowing these files to be committed to the repository. This ensures everyone is using the same versions of dependencies for consistent, reproducible builds.Describe alternatives you’ve considered
Relying on the hope that no dependency introduces breaking changes and that all maintainers adhere perfectly to semantic versioning. However, this is often unpredictable in practice and can result in compatibility issues.
Additional context
Lock files serve as a record of exact dependency versions. Including them in version control helps avoid unintentional mismatches and ensures consistent environments for all contributors.
The text was updated successfully, but these errors were encountered: