-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unpacking application into custom folder #273
Comments
Facing the same issue - is there any workaround? |
@theRaja It seems its not issue of nw-builder but nw.js itself see nwjs/nw.js#815. When nw.js dealing with packed app.nw or even bundled together with nw.exe it is unpacking it into temp folder by default and I was not able to find any option to override this default behavior. We were able to come up with 2 workarounds.
Hope this helps and also if you come up with way how to overcome this nw.js default behavior, let me know. |
I agree that this is not an issue with nw-builder. |
We have created nw application which persist data in local sqlite database.
Problem when using nw-builder is that once user run's application it will create new temp directory. Every change is persisted to local db in this temp folder, but when user open application again different temp directory is created and changes from from db are lost. (in different unknown temp folder)
Is it possible to tell nw-builder when unpacking to use custom directory? Or at least same temp everytime?
Why is it using temp in first place? Couldn't it just unpack needed files in current dir?
Thanks for any info.
The text was updated successfully, but these errors were encountered: