Package Details: tidal-hifi-git 7.0.0.r0.gb21d415-1

Git Clone URL: https://aur.archlinux.org/tidal-hifi-git.git (read-only, click to copy)
Package Base: tidal-hifi-git
Description: The web version of tidal.com running in electron with hifi support thanks to widevine. If the install fails use nvm to temporarily downgrade npm
Upstream URL: https://github.com/Mastermindzh/tidal-hifi
Keywords: hifi tidal tidal-hifi
Licenses: custom:MIT
Conflicts: tidal-hifi
Provides: tidal-hifi
Submitter: mastermindzh
Maintainer: mastermindzh
Last Packager: mastermindzh
Votes: 13
Popularity: 1.36
First Submitted: 2021-06-26 14:03 (UTC)
Last Updated: 2026-05-11 09:42 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

cocoelacanth commented on 2026-01-26 21:20 (UTC) (edited on 2026-01-26 21:21 (UTC) by cocoelacanth)

The build process seems to be unaware of my existing nvm installation. I used the official install script at https://github.com/nvm-sh/nvm, but makepkg still attempts to install it as a dependency.

The PKGBUILD runs command -v nvm to check if nvm is already sourced. If nvm is installed locally (i.e. located in the home folder and sourced in .bashrc), this will inevitably fail. The subsequent check for nvm in /usr/share/nvm also only works if nvm is installed via pacman.

As a result, following the build, I have two nvm installations on my system: one in ~/.nvm, and one in /usr/share/nvm.

It may be a good idea to add a check for $NVM_DIR to the PKGBUILD so makepkg can detect a local installation.

cocoelacanth commented on 2026-01-14 21:24 (UTC) (edited on 2026-01-14 21:31 (UTC) by cocoelacanth)

When building this package, I get the following npm warning:

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'tidal-hifi@6.0.1',
npm warn EBADENGINE   required: { node: '>=24.12.0', npm: '>=10.0.0' },
npm warn EBADENGINE   current: { node: 'v22.22.0', npm: '10.9.4' }
npm warn EBADENGINE }

The package still builds and installs fine, but it appears that the PKGBUILD is still using lts/jod (Node 22) rather than lts/krypton (Node 24).

That1Calculator commented on 2026-01-12 16:46 (UTC) (edited on 2026-01-12 16:46 (UTC) by That1Calculator)

Got this error while trying to upgrade:

> tidal-hifi@6.0.1 builder
> electron-builder --publish=never -c ./build/electron-builder.pacman.yml

  • electron-builder  version=26.4.0 os=6.18.3-2-cachyos
  • loaded configuration  file=/home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/build/electron-builder.pacman.yml
  • loaded parent configuration  file=/home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/build/electron-builder.base.yml
  • writing effective config  file=dist/builder-effective-config.yaml
  • executing @electron/rebuild  electronVersion=39.2.4 arch=x64 buildFromSource=false workspaceRoot=/home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi projectDir=./ appDir=./
  • installing native dependencies  arch=x64
  • preparing       moduleName=@parcel/watcher arch=x64
  ⨯ The "path" argument must be of type string. Received undefined  failedTask=build stackTrace=TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:387:5)
    at validateString (node:internal/validators:162:11)
    at Object.resolve (node:path:1098:7)
    at NodeGyp.rebuildModule (file:///home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/@electron/rebuild/lib/module-type/node-gyp/node-gyp.js:91:39)
    at async ModuleRebuilder.rebuildNodeGypModule (file:///home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/@electron/rebuild/lib/module-rebuilder.js:90:9)
    at async ModuleRebuilder.rebuild (file:///home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/@electron/rebuild/lib/module-rebuilder.js:124:16)
    at async Rebuilder.rebuildModuleAt (file:///home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/@electron/rebuild/lib/rebuild.js:158:13)
    at async Rebuilder.rebuild (file:///home/kainoa/.cache/yay/tidal-hifi-git/src/tidal-hifi/node_modules/@electron/rebuild/lib/rebuild.js:101:17)
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: tidal-hifi-git-exit status 4

mastermindzh commented on 2025-09-16 07:06 (UTC)

@chadsr, done :)

chadsr commented on 2025-09-15 15:41 (UTC) (edited on 2025-09-15 16:10 (UTC) by chadsr)

Firstly, thanks for maintaining this!

I noticed this PKGBUILD is still using lts/gallium, which is causing build warnings. Updating to lts/jod would be great.

Edit: alternatively, since you provide an .nvmrc, you could just modify the script to use whatever version is listed there.

mastermindzh commented on 2023-03-07 14:55 (UTC)

Sorry, I already fixed it but never successfully pushed. A second release should be up now with the fix.

Idk why it added <> last time, I always use the same build command :/

HarmfulBreeze commented on 2023-03-07 14:35 (UTC)

Hi, I think the .SRCINFO needs to be fixed. Indeed the source and url fields seem to be in a format that cannot be understood by yay. I think removing the <> should be enough.

makepkg --printsrcinfo > .SRCINFO fixed that for me.

deimidis commented on 2023-01-31 21:33 (UTC) (edited on 2023-01-31 21:53 (UTC) by deimidis)

Hi, I'm having errors at prepare

==> Iniciando prepare()...
found init-nvm.sh in /usr/share/nvm, sourcing...
==> ERROR: Se produjo un fallo en prepare().
    Cancelando...
 -> error compilando: tidal-hifi-git

How can I get more info to know which is the problem? (I'm on Manjaro)

mastermindzh commented on 2023-01-31 10:56 (UTC)

Hey @aiyion,

I don't mind removing it, but "makepkg --printsrcinfo" adds them automatically so I'd have to extend the script that builds it :)

aiyion commented on 2023-01-29 11:21 (UTC)

@mastermindzh Would you mind removing the '<' and '>' from the upstream url? At least paru complains on "fatal: protocol '<https' is not supported".

1 2 3 4 5 Next › Last »