@George Is this still true? I'm running custom extensions with external modules with no problems.
It is only needed if you need special native node modules, but even then if those are Napi compatible, it might work all fine.
I see. Thanks. Nearly all my custom extensions still work so that’s great.
There is only one that doesn’t: one that uses bytenode.
I have this precise issue:
Have you guys encountered this with your implementation?
We actually have bytenode included and use it now very extensive as part of our speed optimization to pre compile a lot.
So it should run but be aware that a recompile will be needed for each different node version.
1 Like
It seems that bytenode doesn’t work with the node version that Wappler is packaging(14.16.0) which is weird as you already told me before it’s being used extensively.
I changed my system local version to 14.16.0 and compiled using this version to try reproduce using “own server” and indeed I was able to reproduce the issue.
However if I changed back to a newer node version(16.13.1) and recompile the file it worked correctly.
Not that it’s critical or anything. But anyway I think it’s worth mentioning.