Package Details: notion-app 2:2.0.16-7

Git Clone URL: https://aur.archlinux.org/notion-app.git (read-only, click to copy)
Package Base: notion-app
Description: The all-in-one workspace for your notes and tasks
Upstream URL: https://www.notion.so/desktop
Keywords: kanban markdown notes task
Licenses: MIT
Submitter: pat-s
Maintainer: jamezrin (Orangutan)
Last Packager: jamezrin
Votes: 32
Popularity: 3.52
First Submitted: 2019-02-27 14:00
Last Updated: 2021-04-16 22:04

Pinned Comments

pat-s commented on 2019-04-07 12:41

If you are missing emoji support, take a look here: https://pat-s.me/post/emoji-support-for-notion-so-on-linux/

Latest Comments

1 2 3 4 5 6 ... Next › Last »

blacksuan19 commented on 2021-04-16 21:24

@jamezrin the symlink points to the app.asar in yay cache instead of the one in resources, even after fixing that notion enhancer doesn't work because /usr/bin/notion-app is missing, symlinking /opt/notion-app/notion to /usr/bin/notion-app doesn't work because its a binary

jamezrin commented on 2021-04-16 20:16

@nfode I also use asdf-vm and I don't have that problem, I might have done something in the past for it to work in that scenario. Anyway, I have reverted that change, it was not necessary.

@materemias electron11 is not needed anymore. You don't need to have electron installed for runtime.

I have made a link so that the app.asar (the file notion-enhancer looks for) is in the same location as previous versions of this package. It might still not work since this package now repackages the whole thing.

If after the new update notion-enhancer still doesn't work let me know and I will open an issue on notion-enhancer.

@Koushik_Sahu thanks for that, I had python2 installed and couldn't reproduce the issue. Now I have a container with a barebones arch install that should allow me to catch these things.

saidneder commented on 2021-04-16 20:01

Hello! thanks for the package jamezrin! Working on Manjaro

begati commented on 2021-04-16 12:17

Based on @Koushik_Sahu's solution, this worked for me with 2:2.0.16-5 package version.

sudo pacman -S python2 npm nodejs-lts-dubnium
sudo npm install -g env-paths request

materemias commented on 2021-04-16 10:47

also could you please make it compatible with enhancer? even with the tweaks mentioned here https://www.notion.so/hack-notion-enhancer-v0-10-2-to-work-with-notion-s-v2-0-13-app-a4ab1267e67b4126b6448641ca4a0041 I see

=== NOTION ENHANCEMENT LOG ===
### ERROR ###
Error: notion installation has been corrupted: no executable found.
     at module.exports (/home/me/.node_modules/lib/node_modules/notion-enhancer/pkg/apply.js:31:15)
     at async CAC.<anonymous> (/home/me/.node_modules/lib/node_modules/notion-enhancer/bin.js:30:5)
=== END OF LOG ===

I think it is missing some basic concepts how enhancer detects installed app... like name of the executable...

nfode commented on 2021-04-16 10:03

In the last commit caching was introduced to npm install

HOME="$srcdir/.electron-gyp" npm install --cache "${srcdir}/npm-cache"

When you use a version manager like asdf for managing nodejs versions, the change of the HOME variable is problematic. On change asdf does not work correctly and results in the following error:

==> Recreating package node_modules...
unknown command: npm. Perhaps you have to reshim?

Is it possible to not use the $HOME variable? Else I have to patch the PKGBUILD myself.

materemias commented on 2021-04-16 09:17

Is electron11 still needed for the latest version?

Koushik_Sahu commented on 2021-04-16 05:59

If anyone is facing npm issues while update, those issues are due to some npm package using python2 syntax. Install python2 with the following command and the update should work fine

sudo pacman -S python2

ehlegeth commented on 2021-04-16 01:43

As @jamezrin mentioned,

the validity check failure for exit-after-windows-closed.patch is resolved by cleaning the yay cache (usually at $HOME/.cache/yay/notion-app) and installing the package again.

Thank you for maintaining this package and fixing the issue.

begati commented on 2021-04-15 23:48

Hi, did you update it? I didn't remember the version I had problem, but the 2:2.0.16-5 is giving me the same error since last log.