when you uninstall dendron, it’ll remove the extensions in the bundle (preview, graphs and snippets)

this is the error message I got when I try to uninstall dendron v0.19.1 "Cannot uninstall 'dendron' extension. 'Dendron Markdown Links' extension depends on this."

bundled uninstall does not seem to work atm means you need to uninstall Dendron Markdown Links first

you're right, i think this is because of a change we made. markdown links & markdown preview both declare a dependency on dendron extension because we have an ordering requirement (dendron needs to start first and initialize the engine and the extensions connect to it) looks like vscode prevents you from uninstalling an extension that has active dependents. will make a note in our docs for uninstallation!

Having an issue where Dendron Randomly greys out the Explorer

I can't open any files, It's fixed sometimes if I restart VSCode, issue doesn't appear if I disable the extention

Is there any way to fix the issue with "still connecting to engine..." when opening "Dendron: Show preview". I have tried to wait, to restart (VSCode and PC) and it doesn't want to show anything. Fixed: After uninstalling Dendron and installing again in VSCode it started working.

does anyone use multipl installations of vscode? mine is currently littered with extensions and I don't want to sit down and clean them up right now 😄 I want to try out dendron in an isolated environment and wondering if anyone else has a similar setup.

usually, i only enable my extension per-workspace so that takes care of the littering issue

I guess I have to sit down and weed out all the globally enabled redundant extensions I don't use anymore this weekend.

Just using portable mode for now.

so a question for publishing. Will we be capable to provide our own templates? I have Looked at 11ty and was happy to discover that it supports pug templates. So what i want to know are we going to be able to provide our own templates / Styles for the publishing using a templating language of our own choosing?

is this operating system specific? the next time this happens, can you DM the logs of the crashed session using these instructions? https://dendron.so/notes/a6c03f9b-8959-4d67-8394-4d204ab69bfe.html#logs-from-previous-session

this is fixed when you close and open preview. the preview extension relies on the dendron extension to call up notes

i use vscodium, vscode and vscode insider 😅 i would just pick one of them that you are not using to test out dendron

I just found out about vscodium today, and homebrew was acting up so I just went for a portable binary of vscode for now.

eventually, that will probably be the case. the current priority is to bring it to feature parity with the current jekyll template which means supporting liquid. you can see the progress here: https://github.com/dendronhq/dendron-11ty

I read up a little about 11ty. Looks dead simple. I was kinda wondering why I have to go through all these hoops to have a static site up while I was using Gatsby.

yeah, was looking at gatsby originally but decided it was just too much

I can see how it's useful for whipping out react apps quickly though.

I've worked on a couple gatsby projects and Im glad you went with 11ty 😄

Im pretty interested in what a dendron-nextjs would look like though

Thank you for your answer. It looks like closing and opening preview doesn't work for me. As earlier I have reinstalled dendron addon and it was working. Now after windows restart again I can't see the preview. I see message as before "still connecting to engine..."

hmm, do other dendron features work when the preview doesn't? dendron is initialized if you open a vscode workspace via the "dendron.code-workspace" file

I've had this issue before today's update though, usually restarting vscodium would fix it, but it's persisting now

I have the same issue quite regularly but I haven't found a repeatable pattern yet. Most of the time a

Reload Window

fixed it. What OS do you use? I'm on Windows.

Arch

Manually disabling the plugin and reloading fixed it

me too :) as for dendron-nextjs - phase 1 is replacing form dialogues with web uis. if you run

> Dendorn Configure

, that web ui is rendered using next.js. - phase 2 is adding GUIs for operations like schema updates as well as alternative visualizations of notes (eg. mindmap) - phase 3 is replacing the current preview with a dynamically rendered one using eleventy/nextjs we might also use nextjs for a managed publishing solution where we can offer features like access control and a web based editor