You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
I've got node 6.11.2 running and npm 3.10.10 which are the same versions that were running on my Mac.
I have two projects from FoundationPress 2.6.2 that I need to continue to maintain and I've cloned the repos for them into my wordpress theme folder (no node_modules are in the repo). When I run npm install I get the following errors:
Please List the Following:
OS & version: Windows 10
Node version (node -v) [Node v4+ is required] : 6.11.2
FoundationPress version (see line 3 in package.json): 2.6.2
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/oasis-connect/node_modules/.staging/extend-17cb941d/CHANGELOG.md'
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/oasis-connect/node_modules/.staging/extend-17cb941d/CHANGELOG.md'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/Users/Philip/test/oasis-connect/npm-debug.log
Edit: Also note I have tried running this with npm install, and as seen in this error log npm i -f and it makes no difference
The text was updated successfully, but these errors were encountered:
It seems this issue isn't just related to the older version 2.6.2...I tried pulling down the most recent version of FoundationPress and doing an npm install and I get the following:
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/FoundationPress/node_modules/.staging/core-js-3e8dcea6/es6/date.js'
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/FoundationPress/node_modules/.staging/core-js-3e8dcea6/es6/date.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/Users/Philip/test/FoundationPress/npm-debug.log
How can this bug be reproduced?
Hoping someone can help here...Recently switched from Mac to PC and have setup WSL following these instructions for getting node setup with nvm: https://daverupert.com/2018/04/developing-on-windows-with-wsl-and-visual-studio-code/
I've got node 6.11.2 running and npm 3.10.10 which are the same versions that were running on my Mac.
I have two projects from FoundationPress 2.6.2 that I need to continue to maintain and I've cloned the repos for them into my wordpress theme folder (no node_modules are in the repo). When I run npm install I get the following errors:
Please List the Following:
npm ERR! Linux 4.4.0-17134-Microsoft
npm ERR! argv "/home/pabowles/.nvm/versions/node/v6.11.2/bin/node" "/home/pabowles/.nvm/versions/node/v6.11.2/bin/npm" "i" "-f"
npm ERR! node v6.11.2
npm ERR! npm v3.10.10
npm ERR! path /mnt/c/Users/Philip/test/oasis-connect/node_modules/.staging/extend-17cb941d/CHANGELOG.md
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall utime
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/oasis-connect/node_modules/.staging/extend-17cb941d/CHANGELOG.md'
npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/c/Users/Philip/test/oasis-connect/node_modules/.staging/extend-17cb941d/CHANGELOG.md'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/Users/Philip/test/oasis-connect/npm-debug.log
Edit: Also note I have tried running this with npm install, and as seen in this error log npm i -f and it makes no difference
The text was updated successfully, but these errors were encountered: