codyhouse / codyhouse-framework

A lightweight front-end framework for building accessible, bespoke interfaces.
https://codyhouse.co/
MIT License
1.16k stars 173 forks source link

(node:18428) ExperimentalWarning: The fs.promises API is experimental #100

Closed starchild closed 2 years ago

starchild commented 2 years ago

Hi,

I'm trying to do a fresh install so I can jupgrade from v1 to v3, and I'm getting this when I run npm install:

npm ERR! code 128 npm ERR! An unknown git error occurred npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/CodyHouse/gulp-sass-glob.git npm ERR! command-line line 0: unsupported option "accept-new". npm ERR! fatal: Could not read from remote repository. npm ERR! npm ERR! Please make sure you have the correct access rights npm ERR! and the repository exists.

Any ideas please?

Thank you

starchild commented 2 years ago

npm -v (node:3660) ExperimentalWarning: The fs.promises API is experimental 7.24.1

starchild commented 2 years ago

I've run npm install npm@latest -g and now the error is:

npm ERR! code 128 npm ERR! An unknown git error occurred npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/CodyHouse/postcss-css-variables.git npm ERR! command-line line 0: unsupported option "accept-new". npm ERR! fatal: Could not read from remote repository. npm ERR!

claudia-romano commented 2 years ago

Hi there, are you trying to reinstall the npm modules on an existing project?

starchild commented 2 years ago

No, fresh install.

claudia-romano commented 2 years ago

ok thanks! What version of npm do you have at the moment?

starchild commented 2 years ago

hi, if you see my posts above is shows all that info. 7.24.1 Thanks a lot.

claudia-romano commented 2 years ago

Hi there, yes but since you then ran the npm install latest, I wanted to make sure there was no issue with npm. Anyway I can see you opened an issue on CodyFrame v3 utility classes so I'm assuming you were able to solve the problem. Is this correct? Thanks!

starchild commented 2 years ago

Hi Claudia,

The issue persists. I was able to work elsewhere with an earlier version I had downloaded using an older version of npm I had at the time.

When I try again now with a fresh install, i still get:

(node:5825) ExperimentalWarning: The fs.promises API is experimental npm ERR! code 128 npm ERR! An unknown git error occurred npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/CodyHouse/gulp-sass-glob.git npm ERR! command-line line 0: unsupported option "accept-new". npm ERR! fatal: Could not read from remote repository. npm ERR! npm ERR! Please make sure you have the correct access rights npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-10-06T01_52_49_499Z-debug.log

claudia-romano commented 2 years ago

Thanks for the info! Could you post the content of the complete log file? /root/.npm/_logs/2021-10-06T01_52_49_499Z-debug.log

Thank you!

starchild commented 2 years ago

Here you go. Ty. npm_log.txt

claudia-romano commented 2 years ago

Thank you! Could this be your case (OpenSSH <7.6)? https://github.com/npm/git/issues/31

starchild commented 2 years ago

Perhaps, we are also running 7.4p1

According to forum posts, you can't update openssh on centos 7 anyway. The issue was not present before updating the npm version.

I can't believe I'm the only one experiencing this.

Can I ask what version of NPM you are using please? I will then try and down grade and see if this fixes it.

claudia-romano commented 2 years ago

I have 6.14.15 at the moment.

Are you using our gulp config file? Because the plugin you are having issues with is the one we use in gulpfile.js to automatically import the style of all components in the style.scss file.

If you are not using that config file, you can remove it from the package.json file.

starchild commented 2 years ago

yes, I use gulp watch and your gulpfile.js - It's crucial.

I'll downgrade and see what happens. Ty

starchild commented 2 years ago

FYI downgrading fixed the issue. Ty for your help @claudia-romano