Github user drod331 commented on the issue:
https://github.com/apache/zeppelin/pull/3243
@jongyoul Honestly, I'm not sure. I don't have a ton of experience with
npm, I just knew that the dependency was breaking my build and changing
package-lock.json locally worked for me. It seems like the right answer here,
thanks to @Savalek , might be bumping npm-run-all in package.json to a newer
version, 4.1.5, which no longer uses the (grand)parent dependency of the
offending library.---
