Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ASAR Problem with gdal
See original GitHub issue- Version: 21.2.0
- Target: mac dmg
We are using the node module “gdal”. When this node module is packaged, it is automatically put into the asar file, however, it needs to access csv files within the module, and cannot do that when it is in the asar file. When I specifically set asarUnpack: ["**/node_modules/gdal/**/*"], gdal is still looking in the <app>/Contents/Resources/app.asar/node_modules/gdal/deps/libgdal/gdal/data directory so I have to manually set GDAL_DATA to the correct unpacked directory ( <app>/Contents/Resources/app.asar.unpacked/node_modules/gdal/deps/libgdal/gdal/data) and then everything works fine. Disabling asar altogether works perfectly.
The node module “gdal” needs to not be included in the asar.
Thank you for your help.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Still relevant.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.