ASAR problem in Electron
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 922
- Forks
- 281
- PR merge metrics
- No merged PRs in 30d
Description
If node-tar is used in Electron environment where asar file support is enabled, the entry names with extension asar will not be written correctly, because Electron uses its own 'fs' library which handles asar files as a sub-directory.
Hence, Electron does offer 'original-fs' library if you want to use asar file as normal file instead of a virtual sub-directory in the modified 'fs'.
It would be good if node-tar supported the 'original-fs' library by demand instead of 'fs' from electron.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how node-tar selects and uses the filesystem when run in an Electron environment with ASAR support enabled. Compare the behavior of Electron's modified fs with original-fs, and verify that archive entry names ending in .asar are handled as normal files without breaking standard Node usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100