Arch Linux User Repository

Update/Edit (10.04.2023): You can now start awakened-poe-trade in a browser window and skip the whole overlay part using the --no-overlay flag.

I'm pinning this comment to provide some basic information about this package and possible fixes:

First of all, I'm not the developer of awakened-poe-trade and just maintain this AUR package. The package builds directly from source, using the steps provided in the upstream Github Action Workflow, and adds a custom .desktop file. Most of the time, getting npm dependency warnings during building is "normal" and can be ignored.

Secondly, awakened-poe-trade on Linux can be a tad experimental. As it stands now, it only works on X11 and wayland is not supported. The overlay itself can also be a bit finicky and as far as i can see, composition MUST be enabled, otherwise we get a black screen.

If you have any problems, the following Github Issues might give some ideas as to how to fix them:

https://github.com/SnosMe/awakened-poe-trade/issues/476

https://github.com/SnosMe/awakened-poe-trade/issues/337

https://github.com/SnosMe/awakened-poe-trade/issues/185

@john_paul Thanks for reporting.

Node has been bumped to v20.

I'm encountering a similar error to one of the earlier reported ones:

error minimatch@10.0.1: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.20.5"

It was solved for me by changing the node version set by nvm in the PKGBUILD to 20 from 18.

@yuriosh

I've bumped node to v18, does it work for you now? Building still worked for me on v16 though... maybe some local npm packagess come into play.

Update (16.06.2024): @ninni, thanks for your work and time, now it builds without errors

Hi,

@ninni: i got this error while building,

error isbinaryfile@5.0.2: The engine "node" is incompatible with this module. Expected version ">= 18.0.0". Got "16.20.2" error Found incompatible module.

As of the latest version (3.20.10008) you can start with --no-overlay and what was formerly the overlay will open in a browser window, allowing it to be used where composition is not available or similar.

@justin8 Interesting, which compositor/DE are you on? Just tried it on sway, and for me, the overlay still has problems to attach to the PoE window.

That being sad, this Github issue might be of interest: https://github.com/SnosMe/awakened-poe-trade/issues/803 There's some work being done to allow awakened-poe-trade to start in a completely separate window.

I'm not sure if it's a recent change or not; but this does actually work on wayland these days. I had to disable my nvm install first to make it build properly; my first attempt it would crash when pressing ctrl+d each time.

I've also found that pressing ctrl+d doesn't always open up the overlay, but pressing shift+space will show the search panel correctly at that point; otherwise it appears to work fine in wayland.

Update/Edit (10.04.2023): You can now start awakened-poe-trade in a browser window and skip the whole overlay part using the --no-overlay flag.

I'm pinning this comment to provide some basic information about this package and possible fixes:

First of all, I'm not the developer of awakened-poe-trade and just maintain this AUR package. The package builds directly from source, using the steps provided in the upstream Github Action Workflow, and adds a custom .desktop file. Most of the time, getting npm dependency warnings during building is "normal" and can be ignored.

Secondly, awakened-poe-trade on Linux can be a tad experimental. As it stands now, it only works on X11 and wayland is not supported. The overlay itself can also be a bit finicky and as far as i can see, composition MUST be enabled, otherwise we get a black screen.

If you have any problems, the following Github Issues might give some ideas as to how to fix them:

https://github.com/SnosMe/awakened-poe-trade/issues/476

https://github.com/SnosMe/awakened-poe-trade/issues/337

https://github.com/SnosMe/awakened-poe-trade/issues/185

Hi, got this error while building the pkg on a fresh git clone of the repository:

yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "~/.cache/yarn/v6/npm-@fortawesome-fontawesome-free-6.1.1-bf5d45611ab74890be386712a0e5d998c65ee2a1-integrity/node_modules/@fortawesome/fontawesome-free/.yarn-metadata.json: Unexpected end of JSON input".

-- edit --

purging ~/.cache/yarn solved the issue... building compleeted with some warning though.

node version has now been bumped to v16. Strangely, building works for me on both v14 and v16