Add GraphNote plugin (jh.GraphNote) v1.0.0

[iamjameshannam]

This PR adds GraphNote, a visual graph exploration plugin for NotePlan.

Features:

• Interactive graph of note links, tags, mentions, and external URLs
• Multiple visualisation modes (force, radial, tree, treemap, sunburst)
• Filtering, rebuild, and navigation back to notes

Commands:

• graphnote
• graphnote-rebuild

Includes required assets:

• plugin.json
• script.js
• d3.v7.min.js

[jgclark]

Overall, now that I've had a chance to actually run it for myself, I can see this is great work.
I do have other suggestions and feature requests, but I'm keen to get it in front of others as soon as possible, so I'll just mention one for now. Which is to have another button (all of which could afford to be smaller) to ignore all Calendar notes. In my case they produce a huge amount of noise, which makes seeing anything meaningful difficult. (I have 2,660 calendar notes and 1,400 regular notes.)

[jgclark]

Thanks for the updates. There's still one outstanding comment that needs to be addressed before I can do a first release. That's the one about using the settings system, rather than suggesting users update the script.js file. Those changes will be lost when the next version is released ... which is why there's a separate settings system available.

[iamjameshannam]

Hi Jonathan, I hope you are well, apologies I haven't been back in touch, a busy new year! Ive pushed a few commits last night, would love to get your feedback! James

…

On Wed, 31 Dec 2025 at 21:53, Jonathan Clark ***@***.***> wrote: *jgclark* left a comment (NotePlan/plugins#711) <#711 (comment)> Thanks for the updates. There's still one outstanding comment that needs to be addressed before I can do a first release. That's the one about using the settings system, rather than suggesting users update the script.js file. Those changes will be lost when the next version is released ... which is why there's a separate settings system available. — Reply to this email directly, view it on GitHub <#711 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF3FN5VIACMIAJDHCWCFGNL4ERAXJAVCNFSM6AAAAACQH7DB72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBSHE2DOMBZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[iamjameshannam]

Hey Jonathan, Happy Sunday! Were the changes okay? James

…

On Tue, 6 Jan 2026 at 13:05, James Hannam ***@***.***> wrote: Hi Jonathan, I hope you are well, apologies I haven't been back in touch, a busy new year! Ive pushed a few commits last night, would love to get your feedback! James On Wed, 31 Dec 2025 at 21:53, Jonathan Clark ***@***.***> wrote: > *jgclark* left a comment (NotePlan/plugins#711) > <#711 (comment)> > > Thanks for the updates. There's still one outstanding comment that needs > to be addressed before I can do a first release. That's the one about using > the settings system, rather than suggesting users update the script.js > file. Those changes will be lost when the next version is released ... > which is why there's a separate settings system available. > > — > Reply to this email directly, view it on GitHub > <#711 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AF3FN5VIACMIAJDHCWCFGNL4ERAXJAVCNFSM6AAAAACQH7DB72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBSHE2DOMBZGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[iamjameshannam]

Good evening Jonathan, Just checking in with this plugin. Is there anything else I need to do? If not, what is the process for it becoming available in the plugin store? Regards James

…

On Sun, 11 Jan 2026 at 20:59, James Hannam ***@***.***> wrote: Hey Jonathan, Happy Sunday! Were the changes okay? James On Tue, 6 Jan 2026 at 13:05, James Hannam ***@***.***> wrote: > Hi Jonathan, > > I hope you are well, apologies I haven't been back in touch, a busy new > year! > > Ive pushed a few commits last night, would love to get your feedback! > > > James > > On Wed, 31 Dec 2025 at 21:53, Jonathan Clark ***@***.***> > wrote: > >> *jgclark* left a comment (NotePlan/plugins#711) >> <#711 (comment)> >> >> Thanks for the updates. There's still one outstanding comment that needs >> to be addressed before I can do a first release. That's the one about using >> the settings system, rather than suggesting users update the script.js >> file. Those changes will be lost when the next version is released ... >> which is why there's a separate settings system available. >> >> — >> Reply to this email directly, view it on GitHub >> <#711 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AF3FN5VIACMIAJDHCWCFGNL4ERAXJAVCNFSM6AAAAACQH7DB72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBSHE2DOMBZGI> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[jgclark]

Apologies for the delay. I was about to action this when without warning the NP dev released the biggest change to the environment for plugins in 2 years. Experience meant that the two main plugin devs had to focus on testing and working with Eduard to sort out the inevitable issues straight away. Particularly as users started asking for us to support the change in the main plugins. And the plugin devs are simply volunteers, and between us we run 3 charities and 1 business.

[jgclark]

So I can now return to GraphNote. The NP changes in v3.20.1 around support for "mainWindow" running for plugin windows and plugin installation methods will mean further changes, sorry. I think they're worth making even before first release, as I know the first piece of feedback will be "can you support running in the main window?".

I commented before that you've submitted just the script.js file, rather than more normal smaller code and module files using flow (or possibly typescript) typing, which are then rolled-up and built into a release package. If you'd delivered it in this way, then I would just make the relatively minor changes to support main window myself, and then show you what I'd done.

I really hoped to release this today, but looking at the code again, I'm not comfortable in updating this single large file, particularly without my usual tooling for roll-up and type checking.

There are also some significant provided helper functions to make it easier to work with the HTMLView APIs that I've developed over the years, and updated in the last 3 weeks. Specifically in helpers/HTMLView.js function showHTMLV2(). From its jsdoc it:

• Automatically provides the user's current NP theme through a complex them-to-CSS translation process.
• Most data comes via an opts object, to ease future expansion.
• Supports running as "main window" (i.e. in Editor) on all platforms, as modal windows on all platforms, and as floating windows on macOS.
• Adds ability to automatically display floating windows at the last position and size that the user had left them at.

To be clear, you don't have to do all of this, but it will mean that you won't get some of the gradual improvements from updated helper functions over time.

So, back to you. How you would like to proceed?

[jgclark]

And, if you're not already on the NP Discord, please join it, and then say hi in the plugin-dev channel. There's been extensive discussion of all this between the NP dev and the plugin devs about window management, which you've missed out on.