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
After 'npm install' into my 'theme' dir I got an error:
npm error code 128 npm error An unknown git error occurred npm error command git --no-replace-objects clone -b v3.4.4 ssh://[email protected]/bigcommerce-labs/node-sass.git C:\Users\***\AppData\Local\npm-cache\_cacache\tmp\git-cloneXXXXXXCv3RMS --recurse-submodules --depth=1 --config core.longpaths=true npm error fatal: destination path 'C:\Users\***\AppData\Local\npm-cache\_cacache\tmp\git-cloneXXXXXXCv3RMS' already exists and is not an empty directory. npm error A complete log of this run can be found in: C:\Users\***\AppData\Local\npm-cache\_logs\2024-11-19T19_33_38_519Z-debug-0.log
Environment
Stencil-cli version stencil --version: 8.4.1
Node version node -v: v20.16.0
NPM version npm -v: 10.9.0
OS: Windows 11
The text was updated successfully, but these errors were encountered:
@VitaliiYelinskyi That's likely because some old version of stencil-cli or node-sass are included as a package dependency in the theme. And that version of the package(s) doesn't support node v20.
Actual behavior
After 'npm install' into my 'theme' dir I got an error:
npm error code 128 npm error An unknown git error occurred npm error command git --no-replace-objects clone -b v3.4.4 ssh://[email protected]/bigcommerce-labs/node-sass.git C:\Users\***\AppData\Local\npm-cache\_cacache\tmp\git-cloneXXXXXXCv3RMS --recurse-submodules --depth=1 --config core.longpaths=true npm error fatal: destination path 'C:\Users\***\AppData\Local\npm-cache\_cacache\tmp\git-cloneXXXXXXCv3RMS' already exists and is not an empty directory. npm error A complete log of this run can be found in: C:\Users\***\AppData\Local\npm-cache\_logs\2024-11-19T19_33_38_519Z-debug-0.log
Environment
Stencil-cli version
stencil --version
: 8.4.1Node version
node -v
: v20.16.0NPM version
npm -v
: 10.9.0OS: Windows 11
The text was updated successfully, but these errors were encountered: