[jira] [Created] (AIRAVATA-2951) Django JS build failure: npm install fails with "enoent ENOENT: no such file or directory..."

["Marcus Christie (JIRA)" <ji...@apache.org>]

Marcus Christie created AIRAVATA-2951:
-----------------------------------------

             Summary: Django JS build failure: npm install fails with "enoent ENOENT: no such file or directory..."
                 Key: AIRAVATA-2951
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2951
             Project: Airavata
          Issue Type: Bug
          Components: Django Portal
            Reporter: Marcus Christie
            Assignee: Marcus Christie


npm install error:

Sporadically npm install and build fails. Could be related to having local package references. Deleting the package-lock.json files seems to fix the issue and the package-lock.json files seem to be the culprit. I'm proposing that we just remove the package-lock.json files since
# I'm seeing a lot of churn in these files. Doing {{npm install}} twice will often result in changes in the file even though that shouldn't be possible. So I'm not even sure what benefit they would provide if there weren't causing build problems.
# We're not the only ones running into this problem and looks like there are still unresolved issues in npm (https://github.com/npm/npm/issues/17722)

Error message:
{noformat}
npm ERR! path /data/portals/django-seagrid/airavata-django-portal/django_airavata/static/common/node_modules/.staging/django-airavata-api-41f718eb/node_modules/ansi-regex
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/data/portals/django-seagrid/airavata-django-portal/django_airavata/static/common/node_modules/.staging/django-airavata-api-41f718eb/node_modules/ansi-regex' -> '/data/portals/django-seagrid/airavata-django-portal/django_airavata/static/common/node_modules/.staging/ansi-regex-67ed7b67'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pga/.npm/_logs/2018-11-19T19_30_32_316Z-debug.log
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)