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.499696
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 »

arash-m commented on 2018-02-13 14:33

Somebody should make a bin version of this package.

clone1612 commented on 2017-10-29 07:33

@zerophase Thanks for the comment. This warning can safely be ignored as the only files affected are package.json files from the individual node modules (e.g. /usr/lib/boostnote/node_modules/ua-parser-js/package.json) which are never used once packaged. However I will look into it to see if the warning can be avoided.

EDIT: Looking at it seems to be npm itself adding these absolute paths even though it doesn't use them. No option to avoid it.

zerophase commented on 2017-10-28 19:16

I'm getting WARNING: Package contains reference to $srcdir when building.

jcstryker commented on 2017-10-09 17:39


Ah that makes sense. I went ahead and blocked it anyway, but it is nice to know its purpose. Thanks for your work.

clone1612 commented on 2017-10-09 16:15

@jcstryker Thanks for the heads up. I verified it and no, it's not analytics related. It's for the bottom notification area which currently shows 'Sync Boostnote data across devices'. They send a request which return a JSON file containing the message that should be shown.

jcstryker commented on 2017-10-09 16:06


I am still getting a connection to on starting the app. Is this analytics related?

clone1612 commented on 2017-10-09 12:53

Fully removed analytics again. People keep having problems with it (e.g. and it's more privacy friendly this way. Much smaller package size is also a bonus.

clone1612 commented on 2017-08-10 15:45

If you have any problems with preferences being reset, please follow the instructions in This release contains a bug that will be fixed when they release a new version (in the coming days) but that post contains a work-around.

EDIT: Problems should be fixed with v0.8.14

clone1612 commented on 2017-07-29 07:12

Updated to v0.8.12, thanks for the advice @NicoHood. For now I've just set tracking to false by default, like you mentioned, while I look at a clean way of removing all analytics (since they changed a bit since my previous removal patch). Should be possible but do not worry even without the removal tracking is disabled by default :)

EDIT: Removed amazon analytics once again, turned out to be easier then first expected :)
If any issues arise feel free to say so and I will look into them.

NicoHood commented on 2017-07-22 06:57

Thanks for the patch!
For the next version:

in the next version you could patch browser/main/lib/ConfigManager.js to set the tracking to false by default. I think in long term it would be complicated to fully remove it. But if you can fully remove it, that'd be better :)