Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BIG MISTAKE...commands that are supposed to work do not work as expected #41188

Closed
ghost opened this issue Dec 15, 2021 · 1 comment
Closed

Comments

@ghost
Copy link

ghost commented Dec 15, 2021

Version

16.13.1

Platform

no command like this dont work!!!!!

Subsystem

тщ

What steps will reproduce the bug?

firstly i installed the recommendation version (as indicated in this issue) few times, and i cant see the placeholder of installed folder in my file system, but commands that i write after works, so i decided that i did it, but unfortunatelly it works not so as it have to work and started everything with mistake after i write next command: npm install -g yo generator-code, and output was
that i cant access to the mkdir file, i cant pin here the issue, cause i have screenshot, after it one person recommended me to installed another version of node file 12. 16.2 pkg, what i have done. and after it tried to write this command again and now i have next mistake:
npm ERR! Unexpected end of JSON input while parsing near '...:"^24.0.13","@types/n'
so... first question is how to uninstall all files that connected with node, cause i just cant understand how to decide this problem by usual way, and i dont have enough information about same problems and i dont know who or what can fix that...
so i have few versions of node files and dont know where in file system they are, and want to delete them and after it reinstall the node file, how can i did it? what command i should write in console to uninstall all files that was installed few times, and different versions? i will hope for your aswer

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response

@Trott
Copy link
Member

Trott commented Dec 15, 2021

Hi. This seems unlikely to be a bug in Node.js core and might be more appropriate to discuss in one of these venues:

@Trott Trott closed this as completed Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant