Perla Al Haddad created ZEPPELIN-5913:
-----------------------------------------

             Summary: npm ERR! err.code.match is not a function
                 Key: ZEPPELIN-5913
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5913
             Project: Zeppelin
          Issue Type: Bug
          Components: build, zeppelin-web
         Environment: I am building this through wsl2 on a windows 10 machine
            Reporter: Perla Al Haddad
         Attachments: NpmErr!err.code.matchIsNotAFunction.log

I've been running into this error when trying to build the project. This is 
happening for the zeppelin-web plugin
{code:java}
[INFO] Running 'npm install --legacy-peer-deps' in 
/home/perla/zeppelin/zeppelin/zeppelin-web
[DEBUG] Executing command line 
[/home/perla/zeppelin/zeppelin/zeppelin-web/node/node, 
/home/perla/zeppelin/zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js,
 install, --legacy-peer-deps]
[ERROR] npm ERR! err.code.match is not a function
[ERROR]
[ERROR] npm ERR! A complete log of this run can be found in:
[ERROR] npm ERR!     /root/.npm/_logs/2023-05-19T09_19_34_604Z-debug.log{code}
 
These are my npm and node versions:
{code:java}
npm --version
6.9.0

node --version
v12.3.1 {code}
I have tried building the project with multiple different versions of node and 
npm and they all throw different errors. But I assumed this would be the most 
correct approach as it follows the versions specified in the pom.xml.
Contents of the pom.xml:
{code:java}
<node.version>v12.3.1</node.version>
<npm.version>6.9.0</npm.version> {code}
The latest test I did was after completely deleting both node, npm, and nvm 
from my system and doing a clean install using the versions specified above.
 
I am building the 10.1 tag on github using this command:
{code:java}
mvn clean package -DskipTests -Pspark-3.0 -Pvendor-repo -rf :zeppelin-web -e -X 
{code}
A more complete traceback of the log will be attached to this issue.
 
This is a major blocker that's preventing me from building the project from 
source. I've been dealing with this issue for a couple days now with no 
meaningful progress. Any help on this would be very appreciated.
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to