Package Details: boostnote 0.11.16-1

Git Clone URL: (read-only)
Package Base: boostnote
Description: Open source note-taking app for programmers
Upstream URL:
Keywords: electron productivity
Licenses: GPL3
Submitter: rokt33r
Maintainer: clone1612
Last Packager: clone1612
Votes: 51
Popularity: 0.521177
First Submitted: 2016-04-11 13:01
Last Updated: 2019-05-22 19:08

Pinned Comments

clone1612 commented on 2018-06-13 06:04

Just an FYI on certain warnings appearing during the installation:

  • Warning about optional dependencies -> Bug in npm ignoring the --no-optional flag (

  • Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file ( These warnings can safely be ignored since package.json is not used after installation.

  • Security alerts -> Upstream issue, I'll try looking into it and fix things where possible

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

clone1612 commented on 2018-06-02 06:48

Hey @elgs, that's not an error related to this package. It's something with your AUR helper due to the recent Pacman update. In the same error appears.

What AUR helper are you currently using?

EDIT: You can try installing pacman-contrib ( and see if that fixes things, since a lot of utilities where switched from Pacman to a separate package.

elgs commented on 2018-06-02 06:07

=> Sources are ready.
:: Building boostnote package(s)...
==> Making package: boostnote 0.11.4-1 (Fri 01 Jun 2018 11:02:59 PM MST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
/usr/bin/pacman: unrecognized option '--color never'
==> ERROR: 'pacman' failed to install missing dependencies.
:: failed to build boostnote package(s)

I ended up with the error message above, but it didn't say which dependencies are missing.

clone1612 commented on 2018-05-26 18:58

Regarding the update to v0.11.5 I need to wait until they tag the release on the source repository (see

timmybee commented on 2018-05-26 06:20

To fix "ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end" you need to downgrade NPM.

sudo npm i -g npm@5.6.0

clone1612 commented on 2018-05-14 11:56

@mani.zaeim Looking at it seems to be an issue related to npm itself if using a version greater than 5.6 (which I'm using currently)

EDIT: I've tested a clean installation with npm 6.0.1 but can't reproduce the issue

mani.zaeim commented on 2018-05-14 09:05

npm WARN deprecated babel-preset-es2015@6.24.1: Thanks for using Babel: we recommend using babel-preset-env now: please read to update! npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end

clone1612 commented on 2018-03-12 15:52

Regarding the update to v0.11.x, this package builds from source on the main repo and the release hasn't been made available there yet. Also, multiple bugs are present and a hotfix will be released tomorrow. I'll update it as soon as the hotfix + source release have been made available.

EDIT: Updated the package to the latest version.

clone1612 commented on 2018-02-25 15:01

Working on updating to v0.10.0 but a bug popped up. Upstream a new way of markdown list insertion was added but the needed file is in a node_modules directory under source control (which makes no sense).

EDIT: Updated with a manual fix for the time being

clone1612 commented on 2018-02-16 07:59

@nvllsvm That seems like no problem, will look into it when doing the next update (possibly sooner)

nvllsvm commented on 2018-02-16 05:07

Any thoughts on changing the boostnote.js shebang to '/usr/bin/env electron'? I'm using a wrapper around electron to automatically set the scaling factor.