The practice I've seen is to always have the `package.lock`/`yarn.lock` file in the repo. This way every developer always has exactly the same dependencies. A PR that updates a dependency should also update the lock file.
This looks good to me. I wanted to ask what the reasons for/against using NPM vs yarn are? I personally use yarn for all my projects as it's faster. JupyterLab also uses Yarn. However, NPM is the more standard tool. [ Full content available at: https://github.com/apache/arrow/pull/2598 ] This message was relayed via gitbox.apache.org for [email protected]
