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
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.
The text was updated successfully, but these errors were encountered:
Now when you create a new component using
dcm init
it'll generate apackage.json
file with your dependencies set to some static version we hard-coded. In the process of creating the componentdcm
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.The text was updated successfully, but these errors were encountered: