Update to work with node v 0.12.0

[benoneal]

As title.

[akshayp]

#235 has some discussion around what needs to happen to make jest work on io.js. A lot of the same fixes will also apply to node 0.12.0

[Artsu]

I'm having the same errors as #249 & #181 but on windows:

Error: Worker process exited before responding! exit code: 3221225477, exit signal: null stderr:

I can't even run the tests on node_modules/jest-cli folder as I get the same error.

[donatasbacius]

Having the same issue as @Artsu

[Johnius]

The same as many write above

node v0.12.0

[koistya]

I'm having this issue when jest silently fails without telling what went wrong:

C:\Projects\react-starter-kit>jest
Using Jest CLI v0.4.0
Waiting on 1 test...
C:\Projects\react-starter-kit>

Using Windows, Node 0.12.0, jest 0.4.0

P.S.: It stopped working after updating to Node 0.12.0, but this issue was silently failing (without writing any errors to the console) was present with Node 0.10, jest 0.2, 0.3

[mindjuice]

I'm seeing the same crash as @Johnius with node 0.12.0 and jest 0.4.0 testing the simple React example.

[Johnius]

Working well on v0.10.36

[pierr]

I got the same issue running jest on windows when I require react as in the default unit test example. I'm on version 0.12 of node.

[smussell]

+1 huge blocker for me, all my tests fail.

[imjul1an]

+1 can't even write them :)

[pierr]

Any news on that?

[xeodou]

+1

[twobit]

+1 tests completely broken :(

[zachariahtimothy]

+1 Here, Tests were fine before node/npm upgrade. :(

[pierr]

+1

[koistya]

Here is a test repo, which can be used to reproduce the issue (fails at least on Windows + Node 0.12 or ios):

https://github.com/koistya/jest-sandbox

[sahas-]

+1, I'm down with this issue too..any workarounds?

==> node --version
v0.12.0

==> npm --version
2.5.1

==> npm test

flux@0.0.0 test /Users/.....
jest

Using Jest CLI v0.4.0
Waiting on 1 test...Segmentation fault: 11

[binarykitchen]

i am sure they have plans - there are lots of commits in the 0.5x branch

[alexprice1]

All our software is written on v0.12.

Do we just have to wait until the merge in order to run tests? Seems kind of bizarre that jest would not support v0.12, especially for almost half a year...

[DmitrySoshnikov]

@chapinkapa, would you consider switching to io.js (and installing Jest form 0.5.x branch), or do you have some blockers in other software that don't run on io.js? We had dependencies issus with 0.12, especially with jsdom which doesn't support 0.12 either.

[alexprice1]

Ah, gotcha. Unfortunately I am at a fairly large company that wants to only use the latest stable branch of Node (for supposed stability). We are using Node 0.12 for several of our servers.

[harryworld]

+1

Works in in 0.10.40, not io.js 2.3.0 with Jest 0.5.0

[mull]

@harryworld works with iojs 2.5.0 at least.

[harryworld]

@mull I tried that, the error mentioned here is gone, but the tests are not all passed due to some libraries not included. For instance:

 FAIL  __tests__/Mutation-test.js (0.39s)
● Mutation Generators › it generates a Set Mutation
  - ReferenceError: Parse is not defined

 FAIL  __tests__/ObjectStore-test.js (0.388s)
● Object storage › it supplies data for all pointers that exist at the same depth
  - ReferenceError: query is not defined

[mull]

@harryworld if Parse is not defined then you need to include it. query is not defined sounds like a missed var.

[harryworld]

@mull Interesting, why the same code base (with Jest 0.4.19) can work in 0.10.40? I did not rm -rf node_modules?

P.S> I'm new to Jest, not sure about its magic yet.

[mull]

I couldn't tell you. I noticed the same thing about a missing var when going from 0.10 to iojs2.5. Can't tell you why. :)

[cpojer]

I'm going to close this out as we won't be able to support node 0.12 unfortunately. A decision that was made for us by jsdom. We'll likely be able to reconcile once node v4 comes out, which should support a reasonable upgrade path from node 0.12.

More explanation: #469 (comment)

[cpojer]

@mull @harryworld indeed, you need to define all variables. I think jsdom became stricter in how it handles the global scope.

[binarykitchen]

guys, just use https://www.npmjs.com/package/gulp-jest-iojs for the time being until iojs v4 has been merged with nodejs

[nkbt]

@binarykitchen not everyone uses or wants to use gulp. So iojs seems to be the only option.

[cpojer]

@binarykitchen How does gulp-jest work on node 0.12?

@nkbt your option is to use:

• jest 0.4 with node 0.10
• jest 0.5 with iojs 2+
• in the future it will be jest 0.6+ with node 4.0+ only.

[chiedo]

@cpojer Could you add something to the Jest docs in regards to the specific version numbers that are needed with the specific versions of node?

Some sort of "supported versions" section would probably be helpful!

I'm on node v4 and Jest doesn't seem to be working here either. I can just go back to node 0.10.0 no problem but just a suggestion!

[cpojer]

@chiedojohn jest 0.5.2 and up works with node 4

[chiedo]

Thanks @cpojer looks like I've got some debugging to do on my end then!

[felix-d]

I'm having problem with jest-cli and npm@3.3.4. All my tests are failing for obscure reasons but they work when installing node_modules/ with npm@2X. Is anybody else tried using npm@3.X ?

[cpojer]

Haven't tried npm3 yet. Seems like this should be its own issue, mind creating one, @felix-d ?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.