-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Installation Problem: [Yarn] #5944
Comments
Could you pls paste the error message you encountered here? much appreciated. |
info fsevents@1.2.4: The platform "win32" is incompatible with this module. |
I am Trubble The New Version Node.js And React-Native (0.55) |
@MITDD6338 could you print the output of your terminal? |
Some INfo And Warning Are There....!!!!!!! |
@MITDD6338 apparently it is installing everything normal and creating the file yarn.lock. Is the problem in running some script in package.json? Apparently no error is occurring in yarn through your print. |
{ |
@MITDD6338 From the screenshot you posted above, we can't see any error there. Why did you say that Yarn Install Does't Not Working? |
D:\OfficeWork\Live Project\Test>yarn add firebase
internal/modules/cjs/loader.js:596 Error: Cannot find module 'D:\OfficeWork\Live Project\Test\node_modules\node-pre-gyp\bin\node-pre-gyp' npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: D:\OfficeWork\Live Project\Test> This Error Generate Using Yarn That Why I am telling In u Yarn Is Nort Working. |
@PriyankaVrma how did you install? You could use choco install yarn which is the safest way to install on windows systems. |
I am also seeing this error. My configuration is Windows 10, node.js v10.5.0, and yarn 1.7.0 and I am trying to run: yarn add gulp@4 --dev on a new project. |
FYI: I still see the error after upgrading to node v10.6.0. |
Still getting this warning on node v10.8.0 and yarn v1.9.4. I have noticed something else which may be useful: Not all packages produce the warning. If I start with a clean project and add the ramda package I do not get the warning, but once I add gulp@4 it appears. If I reverse the order by adding gulp@4 first and add ramda second, then the addition of ramda also produces the warning as does adding any other package (it seems). I assume this is because yarn is validating that all existing packages are up to date and it is re-discovering the problem with gulp@v4 each time. I get the same behavior with or without the --dev switch. Furthermore, if I try the same thing with npm I also get the warning:
It exhibits the same behavior as yarn when reversing the installation order: ramda (no warning), gulp@4 (warning) and in reverse: gulp@4 (warning), ramda (warning). There is a gulp issue for this warning also and they have elected not to fix it: There is another issue addressing this 'warning' for yarn and it was resolved by changing the 'warning' to an 'info': However, in my opinion the 'info' message still sounds like a warning and causes people like me to waste time searching for a resolution so they don't have to see this output. A message similar to the following would be better (also note that it should be a single line output instead of two lines):
Furthermore, I only want to see this warning when installing a package that has the dependency on 'fsevents'. I do NOT want to see it when I am installing ramda or anything else that does not use 'fsevents'. It would also be even better if there were a way to silence/hide this specific warning (and perhaps others). Perhaps a way to tell yarn to always ignore this specific package for a given project or perhaps a command line switch for the add command to hide the message. Another possibility would be to only expose the message to developers with a direct dependency and silence it if the dependency is indirect. |
Try this |
Hi @MITDD6338 -- is this still a problem? If so, please comment and update with a detailed description. Otherwise, closing for now. |
I Am Using Windows 10:
Yarn Install Does't Not Working :
The text was updated successfully, but these errors were encountered: