give the same error.
I think your previous problem is related to this (the error is probably related to a faulty build)
The working setup was probably an older docker image that was correct.
Maybe you changed something on your package.json?
You may try 'docker build --no-cache ...' in order to confirm it is not a weird caching problem
There is a way to spot the problem? This is driving me crazy
Обсуждают сегодня