Asar packaging about punk HOT 3 CLOSED

I'll just copy this here from electron/asar#55 (comment):

In my case, the dependency calls .chdir(__dirname) so I decided to use --unpack-dir flag to unpack this specific dependency. The result was:

• app.asar.unpacked folder - this folder contains that one dependency I unpacked
• app.asar file - according to asar list command, this file still contains the dependency as well 🤔

When the code is executing, __dirname points to folder inside app.asar (no idea why, it should be app.asar.unpacked ❓) and so it fails once again. If I place a breakpoint and modify __dirname to contain app.asar.unpacked, it works.

So far I have tried:

• unpackDir: '**/steam-resources/**/*' - unpacks only steam-resources and everything that's inside
• unpackDir: 'node_modules/steam/**/*' - unpacks steam and everything that is inside
• unpackDir: 'node_modules/**/*' - unpacks everything in node_modules

No matter what, the __dirname here always points to app.asar. According to asar list, the folder was also always contained inside app.asar.

from punk.

Tested on both Windows and OSX, results are same.

Here's a small repro case I created: https://github.com/scholtzm/electron-asar-dirname-issue

Reported here: electron/electron#8206

from punk.

1463494

from punk.