I've updated the package.json to use the released kredits-contracts v5.5.0
but if i do an npm install there are loads of changes in the package-lock file (some lodash changes, camelcase version change, etc.) which I did not want to push.
Could you push an updated package-lock?
I've updated the package.json to use the released kredits-contracts v5.5.0
but if i do an `npm install` there are loads of changes in the package-lock file (some lodash changes, camelcase version change, etc.) which I did not want to push.
Could you push an updated package-lock?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently depends on an unreleased version of
kredits-contracts(which also fixes the broken profile updates).@@ -13,3 +11,3 @@.then(() => this.transitionToRoute('index'))return this.kredits.addContributor(contributor);}Does this stay on the form page now, or is the transition happening somewhere else when editing or creating a new contributor?
@@ -13,3 +11,3 @@.then(() => this.transitionToRoute('index'))return this.kredits.addContributor(contributor);}Yes, I moved it to the component:
https://github.com/67P/kredits-web/pull/156/files#diff-05b2a32d1311a3737ec444f68955ccedR81
I've updated the package.json to use the released kredits-contracts v5.5.0
but if i do an
npm installthere are loads of changes in the package-lock file (some lodash changes, camelcase version change, etc.) which I did not want to push.Could you push an updated package-lock?
@bumi OK, cool. I just ran
npm installand only got thekredits-contractschange.