Maël Nison

There's already an open RFC discussing this feature, here: - https://github.com/yarnpkg/berry/issues/2751 It's still waiting for npm to join the discussion there, and I'm not interested to contribute to another RFC...

> Is there a Yarn PR we can follow along? Yes, it would be - https://github.com/yarnpkg/berry/pull/3981

Thanks, I'll check this. It however seems that `copyasm` is copying my `nbind.node` file (instead of `nbind.js` and `nbind.js.mem`).

Is there a synchronous API ? I'm not sure asynchronous APIs are Webpack cup of tea (ideally, it should be able to resolve every module at build time, and chose...

A workaround is to use pointers, as mentioned in #15. However, a better alternative is to use `std::unique_ptr`, so that those pointers will be automatically disposed. ```c++ std::unique_ptr fnPtr; fnPtr...

Hm, the move constructor isn't really necessary, but the assignment operator is interesting because it's the only way to reassign the callbacks attributes of a class instance (otherwise, using pointers...

It's apparently an header issue - I've manually included `nbind/BindDefiner.h`, and it compiled.

Supporting these data structures would be awesome, especially when porting already-existing libraries, where changing data types might not be easy. Somewhat related: when I tried returning `std::unordered_set` and `std::unordered_map` instances,...

Nevermind, I just go too fast, and read the documentation too little ... For anyone with this issue: `toJS` & `fromJS` !

I still feel like more things should be catched at compile time, maybe by adding `static_assert` here and there to check that methods are implemented, or data structure supported.