Closed vorburger closed 6 years ago
with a local s2i
actually this now happens even without S2I when runing pure locally, AFTER (due to #28) doing:
rm -rf scratch/.gradle/ scratch/node_modules
From what little I understand of node, perhaps this is interesting and doesn't seem right:
> Task :scratch:npm_install UP-TO-DATE
...
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
wondering if this could be an impact of #60 ?
no it's not, this problem still happens even after a revert of #60 like this:
git revert eb6ee408e1b6d69082f975a10ecdf1fb89793b8b
but with a fresh git clone
or complete clean like this AT THE ROOT, not in scratch/
it works again:
git reset --hard; git clean -d -f -x
What is weird is that once I did this, it now always works again, every time.
Could this have anything to do with that weird package-lock.json
file? Is this a good idea:
npm WARN conflict A git conflict was detected in package-lock.json. Attempting to auto-resolve.
npm WARN conflict To make this happen automatically on git rebase/merge, consider using the npm-merge-driver:
npm WARN conflict $ npx npm-merge-driver install -g
@edewit while trying to reproduce #70 with a local
s2i
I've hit this, inscratch/
not even inscratch3/
:wondering if this could be an impact of #60 ?