The V8 platform used by this instance of Node does not support creating Workers

[AwesomeNameMan]

Describe the bug
Updated from camaro 5.0.3 to 6 (6.0.3). Using camaro with electron to parse many XML strings.
After the update electron crashes with the following error:

The V8 platform used by this instance of Node does not support creating Workers

Minimal Script To Reproduce

import { ready, transform } from 'camaro';

await ready();
result = await transform(files[fileName], template);

Expected behavior
Camaro not breaking my electron app.

• camaro version: 6.0.3
• Node version: v12.18.3
• Operating system: Windows 10 Version1909 (Build 18363.900)

[tuananh]

Looks like it's similar to this electron/electron#18540 but lemme dig deeper into this. I've never use Electron before.

[AwesomeNameMan]

Thanks for the quick reply, tuananh!

Here some more info about the environment:

• electron version: 9.2.1 (had version 7.x.x before, but same behavior)

I'm distributing the camaro.wasm to the app after build and I've seen you added a worker.js with v6, which seems to break the electron app. As far as I know, electron uses his own node & V8 engine version.

[kentico-ericd]

I'm also having an issue that might be related. I'm writing a Zapier CLI application and started getting this error immediately after trying to call transform()

Error: Cannot find module '/node_modules/piscina/dist/src/worker.js'

[tuananh]

@kentico-ericd what node / camaro version are you using?

[kentico-ericd]

I tried

• camaro 6.0.3
• node 10.22.0

Does it require node >=12? I think it might have been an issue with zapier-platform-core actually- if so, sorry for polluting the thread and I'll check with them :)

[AwesomeNameMan]

Workers should be stable with node >= 12.

@tuananh is it maybe possible to make the usage of workers for camaro optional? This could help with different environments and people can't argue about a lack in performance when workers are not in use.

[tuananh]

I might as well do that :)

…

On Fri, Sep 11, 2020 at 18:21 AwesomeNameMan ***@***.***> wrote: Workers should be stable with node >= 12. @tuananh <https://github.com/tuananh> is it maybe possible to make the usage of workers for camaro optional? This could help with different environments and people can't argue about a lack in performance when workers are not in use. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#116 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEZETWCKTSP52TSONR4BO3SFIB2FANCNFSM4QLQJPDA> .

[tuananh]

Fixed by #122

[AwesomeNameMan]

Problem still occurs for me with the following versions:

• camaro 6.1.0
• Electron 10.1.3

The V8 platform used by this instance of Node does not support creating Workers

[fabiospampinato]

Stil happening v12

[tuananh]

@AwesomeNameMan @fabiospampinato do you have minimal project so that I can try? I'm not very familiar with Electron.

[fabiospampinato]

Oh sorry I thought we were in electron's repo here 🤦‍♂️ my bad. You can probably reproduce the issue by running this library inside Electron's renderer process.

[AwesomeNameMan]

Hi tuananh,

any news here?

[tuananh]

Sorry i didn't have bandwidth for tis project lately. could you rollback to v3 where worker isn't used yet?

[absir1949]

@tuananh i use camaro 3.0.19 There are still problems.

 error: \\?\C:\Users\cd\AppData\Local\Temp\3809f2b1-9563-44e0-8d63-6b5673ffc4d6.tmp.node is not a valid Win32 application.

• camaro 6.1.0,6.2,5.0
• Electron 11.5
• node 12.18.3

[ryan-mooore]

I am having a similar problem trying to use the package in a Next.js server action:

⨯ uncaughtException: [Error: Cannot find module '.../.next/server/vendor-chunks/worker.js'] {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}```