Niklas Gollenstede

I know that line of code, it is in the `multiport` module and definitely does not contain a syntax error. Even if `value.name` happens to be `Function` it won't throw...

Oh, wait. The error you see was re-created after serialization in that line. The actual SyntaxError will be somewhere in your node-side code. The original stack trace *should* be restored....

Give me one more hour and I will upload an actually working, documented example extension ...

Here we go. You should probably have a look at the commit diff regarding fixed errors in the documentation. The example is in `examples/1` and has its own description. Feel...

Ah, yes. Unfortunately, the CI service I use (appveyor) doesn't support macOS. Since I want to change some other things (use a proper installer software that installs unmodified node.js versions),...

I'd love to see that / hear more from you! Just linking to the project homepage (with a unnecessary redirect on top of that) was bad. I had originally just...

Little update here: AppVeyor plans to provide MacOS build VMs "[later this year](https://help.appveyor.com/discussions/questions/23413-are-there-plans-to-make-mac-os-images-available)", so there should be MacOS builds of the NativeExt application part reasonably soon.

> It's a bit of work Oh yes. I've added a minimal example and updated/improved the documentation though. I hope that helps. > need Mac support (my add-on is actually...

Yes, I updated the [README](https://github.com/NiklasGollenstede/native-ext#architecture) to detail that: > The NativeExt project is [...] split up in three parts: > > * the application itself, which is basically just the...

> require users to install both and app and a browser extension. Asking them to install NativeExt to and allow it access is definitely more than I think most people...