-
Notifications
You must be signed in to change notification settings - Fork 396
Develop does not build without lock-file #778
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
Comments
I don't think some minor/patch version updates do break the build. This should not be the case. So please figure out what package version requirement is incorrect. The line of code which is causing you issues was updated in combination of a minor version bump of So please do some research on which package is the issue for you. |
Have you tried building without the lock file? Remove the node modules folder and run For now we are sticking with 6284a5f till this is fixed. |
Removing the lock file and running I am not sure it it is a bad practice to build with a lock file. But lets skip that point here. When checking the new generate lock file in combination with the build errors, you could also have noticed a patch bump of The error shown is introduced in |
Description
When building a library as a dependency the lock file in this repo is not honored. This is expected behavior. Unfortunately with the current versions specified in the package.json this library will not build. Even though your CI builds since it is using the lock file. FYI libraries should not commit their lock file for this exact reason. yarnpkg/yarn#838 (comment)
Build Error
Below is the build error
Lock File Diff
Below is the diff between the committed lock file and one generated fresh.
Solution
Ideally the package.json should be updated to reflect the required versions of dependencies.
The text was updated successfully, but these errors were encountered: