Electron build with asar and native modules causes a path resolve error #114

2xAA · 2020-05-22T23:58:25Z

Fix: disable asar. CHUNKY APPS INCOMING.

2xAA · 2020-05-23T13:59:22Z

Disabling asar may be premature. Making sure __dirname is the same between the worker and the renderer process is key here, then grandiose should be able to find the bindings.

Though finding the correct configuration for this is proving difficult.

… & electron & workers This is an abominable hack which works around the fact webpack just does whatever the fuck it wants with workers. We stall everything in the worker until we've sent it the correct path to the .asar, then in the NDI store module we temporarily set the location of grandiose within the .asar. Guaranteed this will come back to bite us in the arse. fix #114

… & electron & workers (#115) This is an abominable hack which works around the fact webpack just does whatever the fuck it wants with workers. We stall everything in the worker until we've sent it the correct path to the .asar, then in the NDI store module we temporarily set the location of grandiose within the .asar. Guaranteed this will come back to bite us in the arse. fix #114

2xAA added the bug Something isn't working label May 22, 2020

2xAA mentioned this issue May 23, 2020

fix(__dirname): adds horrible wrapper hack for __dirname with webpack… #115

Merged

2xAA closed this as completed in #115 May 23, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Electron build with asar and native modules causes a path resolve error #114

Electron build with asar and native modules causes a path resolve error #114

2xAA commented May 22, 2020

2xAA commented May 23, 2020

Electron build with asar and native modules causes a path resolve error #114

Electron build with asar and native modules causes a path resolve error #114

Comments

2xAA commented May 22, 2020

2xAA commented May 23, 2020