Joplin-vscode-plugin roadmap

Pre Release 0.8.2

  • fix: fix the bug that the title is not set correctly when creating an attachment
  • chore: build.js => build.ts

ref: Release joplin-vscode-plugin@0.8.2 · rxliuli/joplin-utils · GitHub

1 Like

joplin-vscode-plugin is now published to the open-vsx service, which is used by the open source alternative to vscode, the plugin can now be seen from here

Thanks to publish-extensions


Published to the vscode addon store, requires vscode@^1.71.0

1 Like

Pre Released 0.9.0

  • feat: support three new commands, show currently referenced note, show referenced note, insert note link
    mpte links
  • feat: support audio and video display in joplin
  • feat: upgrade joplin-api, no longer rely on node-fetch/form-data, and fill in by itself

Thanks to the update of vscode@1.72, now vscode can view audio and video again, but there are still some problems, including mp4 video without sound, the progress bar cannot be dragged and so on, waiting for the follow-up vscode to solve, ref:



Released 0.9.1, sync to vscode marketplace

  • fix: fix the issue that uploading a file without specifying a filename will cause a mime error
  • feat: update dependency nodejs to 18, no longer include fetch/FormData polyfill

ref: Release joplin-vscode-plugin@0.9.1 · rxliuli/joplin-utils · GitHub

Now, after 47 versions, I think the integration of joplin in vscode is basically complete, and it should only require some maintenance, so 1.0.0 is released

ref: Release joplin-vscode-plugin@1.0.0 · rxliuli/joplin-utils · GitHub


Excellent plugin! Belongs to my daily drivers!

1 Like

Released 1.0.1

By the way, joplin-api released 0.5.0 with support for esm/cjs (esm first)
ref: joplin-api - npm

At the same time, the documentation is regenerated, and now it looks a little more comfortable


The number of installations exceeded 10k ヾ(≧▽≦*)o


Pre released 1.1.0



Thanks for updating this useful plugin. For your awareness, I would like to mention that I am using VScodium instead of MS VSCode, and this fork working well with your Joplin-vscode-plugin.


Release 1.1.1

Fixed the error that baseUrl was not used when checked joplin clipper service, ref: [Bug]: token/port setting is ignored · Issue #67 · rxliuli/joplin-utils · GitHub

Posted on producthunt!

joplin-vscode-plugin - Editing and management of Joplin notes with VSCode | Product Hunt

1 Like

Release 1.1.2

ref: Release joplin-vscode-plugin@1.1.2 · rxliuli/joplin-utils · GitHub

Is there a way to merge this post with the previous one? I realize that splitting into two posts is not a good thing, I generally post the version here, but someone else asks the question in another thread. @laurent

previous post: Joplin's vscode plugin is released!

I don't think we can merge posts, but if you want we can lock the other one?

Ok, maybe lock this thread, I well update and answer questions in another post

Ok, so just to be sure, should I lock "Joplin-vscode-plugin roadmap" or "Joplin’s vscode plugin is released!"?

Joplin-vscode-plugin roadmap

1 Like