-
Notifications
You must be signed in to change notification settings - Fork 4
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
bump node version to 16 #21
Conversation
Started test build 84333 |
Build 84333 failed |
with flatpak-node-generator as of c278045d7cc73437945b3dfb919fc7aea5d43cb5 python3 -m flatpak_node_generator yarn ~/vcs/lossless-cut/yarn.lock --output ~/vcs/no.mifi.losslesscut/generated-sources.json This also requires a change in the build definition to include the yarn configuration.
Started test build 25868 |
Yarn is built in now, isn't it?
Build 25868 failed |
Started test build 25870 |
the new generator produces a setup file that makes it work. Inspired by https://github.com/flathub/net.cozic.joplin_desktop/blob/8aad869adfc541c07a9284aad33aad59165b1a33/net.cozic.joplin_desktop.yml#L74
Started test build 25873 |
Build 25873 failed |
Build 25870 failed |
Started test build 25901 |
Build 25901 failed |
weird. Somehow, the yarn.lock file in the lossless-cut repository got changed. Now it corresponds to the 3.52.0 tag. dd1b44f2d3d645056df78175b421aff414b103e2
Started test build 25912 |
Started test build 25915 |
Build 25912 failed |
Build 25915 failed |
Started test build 25922 |
Build 25922 failed |
I wonder why this is necessary, though, because we're calling pack-linux and there is a "prepack-linux" script defined. Let's see whether this works.
Started test build 25930 |
Build 25930 successful
|
The app works. Thanks @catsout. But there's a big ASAR file, despite electron-builder complaining about the lack of ASAR:
I wonder how to make it not produce an ASAR file. @catsout why does this work for you? |
hm. Thanks. It's gone from here, though: https://github.com/laurent22/joplin/blob/dev/package.json What happens to the arguments? Are they simply appended to the target? i.e. |
Started test build 25934 |
Build 25934 successful
|
looks better now. |
I think the modern generators take care of those.
Started test build 25944 |
we call the packing with the --config.asar=false flag which makes it work better.
Started test build 25945 |
the file is automatically generated now.
Started test build 25946 |
Build 25944 successful
|
Build 25946 successful
|
Build 25945 successful
|
No description provided.