AsyncWrap init hook threw about trace

[AndreasMadsen]

I have published:

• 2.2.1 with a better engines field that supports ^5.3
• 2.0.2 with a better engines field that supports ^4.0

2.0.2 unfortunately don't have a fix for #17, that is not possible without the new features.

Also, I don't plan to continue doing legacy updates. But hopefully it shouldn't be necessary when 4.2.5 gets released.

[AndreasMadsen]

Try using node 5.3.0 there are some required internal features that node 4.2.4 doesn't have. However I have been promised that they will land in version 4.2.5

[julien-f]

You should:

1. express this requirement in package.json in the engines.node
2. maybe even detect this at module startup and throw, because currently there is no way to handle this error and to fail gracefully (i.e. continue without trace).

[AndreasMadsen]

I'm not aware of a syntax that can set independent node version requirements for both v4 and v5. How does that look?

In any case the commits have already landed in v4-staging, so it is a very temporary issue: nodejs/node#3461 (comment)

[julien-f]

node: '^4.2.5 || ^5.3' should work.

What about code already using trace but before 4.2.5?
Currently the program aborts and it is not handled by a try-catch…

[AndreasMadsen]

They should not upgrade to 2.2.x

[AndreasMadsen]

I guess semver was violated to that regard, I'm sorry about that. It is hard to keep track of when trace uses node internal API.