I have some work to do in AsyncWork, like transforming c struct into v8::Object. So I have to write v8 code in AsyncWork.
How can I manage this?

in 06_objects/run.js , if I change:

var obj = new modulename.MyObject(42);

to:

var obj = modulename.MyObject(42);

I get:

Assertion failed: (handle->InternalFieldCount() > 0), function Wrap, file ../src/node_object_wrap.h, line 62.

naturally, this is not the intended usage, but a Javascript error would be nicer than a c++ assertion failure

https://strongloop.com/strongblog/node-js-v0-12-c-apis-breaking/

If the examples will not be fixed for this the main readme should at least have a link there.

shouldn't we close the scope in AsyncAfter since we also opened one?

Why assign the baton to baton.request when you can also assign the baton to you uv_workt_t request? Or is this just convention?

I really appreciate this tutorial, excellent work, and so necessary.

It'd be helpful to have a folder with a complete module template including:

• a module constant (e.g. module.CONST)
• object constructor defining member variable with default value
• sync object method returning an array of sample values: [ 123, 'string', true, null, { m:1 }, new Buffer('stuff') ]
• async object method with a baton & baton subtype, and TryCatch for callback invocation
• uv_async use from the thread pool routine (maybe this is a separate tutorial folder)

And provide limited comments to document where the user should add further definitions and logic.

If you like the idea, I'd be glad to submit patches...

Problem 1)
You call ObjectWrap::Unwrap, which grabs the original pointer from This().
Shouldn't it be using Holder() and not This() ?

Problem 2)
Your 06_objects example is missing a critical part of the example - v8::Signature for type safety.
see line 489 here:
https://github.com/laverdet/node-fibers/blob/master/src/fibers.cc

Problem 3)
You create a Persistent global handle for constructor, and then do nothing with it.
This example also won't work for other v8 embedders who might be using v8 in multiple Isolates and threads.

Instead, it should be a plain Local handle (no global constructor handle), and use the Signature technique to ensure type safety.

I see your node-blend, and it use a eio_req instead what you presentation said uv_work_t, I want to know what's the different between them.

Thanks a lot.

The README.md files for the examples say to run:
npm build

Doing this does nothing on node.js 0.10.26. However, if you do:
node-gyp configure
node-gyp build

It builds the C++ and then do:

node run.js

You are able to use the examples. You may want to update the docs since in general the people using these examples are total newbs to building native C++ extensions for node (like me!). Thanks a lot for contributing these examples.