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

When initializing a new component dependencies versions should be up-to-date #71

Open
eladav opened this issue Aug 13, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@eladav
Copy link
Contributor

eladav commented Aug 13, 2019

Now when you create a new component using dcm init it'll generate a package.json file with your dependencies set to some static version we hard-coded. In the process of creating the component dcm can check on npm and see what is the latest version that makes sense and initialize the component with that (i.e. there should be some strategy other than taking the latest but not something too complicated...)

See the code here. Instead of setting RN version to 52, we can now use 60. This can be done for every dependency in package.json files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant