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

npm run test gives error #6798

Closed
Praneetha-CK opened this issue Apr 11, 2019 · 7 comments
Closed

npm run test gives error #6798

Praneetha-CK opened this issue Apr 11, 2019 · 7 comments

Comments

@Praneetha-CK
Copy link

Praneetha-CK commented Apr 11, 2019

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes.
NPM version - 6.9.0

Which terms did you search for in User Guide?

Running tests

Environment

System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-5575R CPU @ 2.80GHz
Binaries:
Node: 8.11.3 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Browsers:
Chrome: 73.0.3683.86
Firefox: 66.0.2
Safari: 11.1.2
npmPackages:
react: ^16.4.2 => 16.8.6
react-dom: ^16.4.2 => 16.8.6
react-scripts: 1.1.5 => 1.1.5
npmGlobalPackages:
create-react-app: Not Found

Steps to Reproduce

(Write your steps here:)

  1. npm test

Expected Behavior

Expected to run App.test.js . and give appropriate results.

Actual Behavior

node[1714] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
Getting this error. I haven't added any libraries yet. This is the first time I'm trying out testing and have been blocked in the first stage itself. Not able to figure out what the issue actually means.

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Screen Shot 2019-04-11 at 10 53 04 AM

Would also like to mention that there is another create-react-app project with a higher version

npmPackages:
   react: ^16.5.2
   react-dom: ^16.5.2
   react-scripts: 2.0.3

in my system. But npm test is working fine as expected. So I believe this is not a system specific issue as the environments for both projects are same.

@heyimalex
Copy link
Contributor

Try brew install watchman?

@tim-rohrer
Copy link

Try brew install watchman?

Does anyone know why watchman is suddenly required?

@heyimalex
Copy link
Contributor

@tim-rohrer I think this is the relevant issue, or maybe the jest issue it links to.

@tim-rohrer
Copy link

tim-rohrer commented May 8, 2019

@tim-rohrer I think this is the relevant issue, or maybe the jest issue it links to.

As I understand things, and am experiencing on my system, this is the more relevant issue. However, in my situation, I'm not on Sierra nor have I been for years. But, installing watchman seems to have solved the issue. That is good.

But, it still isn't clear to me what is actually requiring watchman?

@heyimalex
Copy link
Contributor

I think jest uses watchman when it's globally installed.

@stale
Copy link

stale bot commented Jun 7, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@stale stale bot added the stale label Jun 7, 2019
@stale
Copy link

stale bot commented Jun 12, 2019

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

@stale stale bot closed this as completed Jun 12, 2019
@lock lock bot locked and limited conversation to collaborators Jun 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants