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

Deprecate in favor of synp #16

Open
k0pernikus opened this issue Feb 13, 2020 · 1 comment
Open

Deprecate in favor of synp #16

k0pernikus opened this issue Feb 13, 2020 · 1 comment

Comments

@k0pernikus
Copy link

k0pernikus commented Feb 13, 2020

This scripts follows a very naive approach, and while this may work for certain projects, it most certainly fails on bigger projects where deleting and reinstalling would lead to a vast amount of upgrades.

Your Readme.md is clear and honest about its behavior, yet it would be helpful to point people to other tools that convert a yarn.lock into a package-lock.json, and synp does just that:

$ npm install -g synp
$ cd project-using-yarn/
$ synp --source-file yarn.lock 
Created package-lock.json
$ rm yarn.lock
$ npm ci
@elbanador
Copy link

Thanks it worked for my project !

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

No branches or pull requests

2 participants