nukeop
nukeop
Do you mean just adding them all to the queue with shuffle enabled?
I've never heard about it until now, but if there's more people who need it, why not. I'll ask on Mastodon.
There's no easy way to identify these, but I want to improve heuristics for stream providers soon.
The latest commits from master build fine on CI: https://github.com/nukeop/nuclear/runs/4991742404 Try these instructions: https://nukeop.gitbook.io/nuclear/developer-resources/development-process And make sure the npm/node versions match.
There's a sort of a circuit breaker that checks if the `local` flag is set and if so it selects the local stream instead of the currently selected stream provider....
We use electron-builder, and I don't see such a configuration option: https://www.electron.build/configuration/win#WindowsConfiguration-target
Nice, then in this case this should only be the matter of adding a flag to the build action so we can generate one more artifact.
It must be this file: https://github.com/nukeop/nuclear/blob/6a99b3f85042f170de840d3e9b9381d8cd5fd84b/packages/app/app/components/LibraryView/LibraryFolderTree/index.js If it was not present at that time, then it could have been broken because of upgraded libraries (notably Electron) - hard to test...
Yes, it's already been finished, I just have to merge it.
I guess so, we haven't merged that in the end.