Skip to content
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

Get a better usage pattern set up for yalc/zalc, which avoids yarn.lock differing between dev machines (eg. working, streamlined yalc retreat/restore) #294

Closed
Venryx opened this issue Apr 18, 2024 · 1 comment
Assignees

Comments

@Venryx
Copy link
Collaborator

Venryx commented Apr 18, 2024

No description provided.

@Venryx Venryx self-assigned this Apr 18, 2024
@Venryx Venryx closed this as completed Apr 26, 2024
@Venryx
Copy link
Collaborator Author

Venryx commented Apr 26, 2024

Achieved the above for the most part... (a bit more flakiness for the yalc-usage process, but better overall, eg. nicer for other devs to have a stable yalc.lock)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

1 participant