@User We're making progress though still plenty left to do. Would love for your input 🙂 So we've migrated our components to AntD - it works well in terms of saving us from building custom components but it does have a large bundle size and makes custom theming more difficult because of the reliance on

less

. As far as next steps in the design-system, the most immediate feature would be showing how different components would look under different color schemes. Currently doing some work to isolate our main components (eg. preview, toolbar, etc) - this should be ready next week. I can ping you at that point if you want to take a crack at putting those components in the design-system! For rush, that's new to me. Will take a look. Lerna has had some learning curves in the beginning but its been working well for us since then

Sure please do! I did notice that some of those ant-d demo websites were pretty sluggish and heavy so was thinking bundle size could be an issue.. When it comes to less and custom theming, that was another challenge I was looking at. They seem to have an option for theming with JS objects so we could look into that. Pls do ping me at that point 🙂

exciting times to be doing vscode development 😇 https://code.visualstudio.com/blogs/2021/10/20/vscode-dev

exciting times to be doing vscode development 😇 https://code.visualstudio.com/blogs/2021/10/20/vscode-dev

I wonder how hard it would be to have Dendron support the browser-only mode? I suspect it would be enough if we run the engine inside the UI instead of spawning a process.

yep, that’s how it was before so that wouldn’t be bad. need to look into how browser mode handles file system calls

anyone know a way to access the dendron-cli version in the cli code itself? yargs lets you set what version of the package should be, and lets you display the version using

--version

option, but doesn't seem like it provides a way to access it dynamically

Incredibly exciting news! Looks like it supports "Live Share", so real-time collaboration with anyone, anywhere a la Google Docs.

Maybe this could help you https://docs.npmjs.com/cli/v7/using-npm/scripts#packagejson-vars, if not you may need to require the

package.json

to get the version that way, Import would not be possible since the

package.json

is outside of the

src/

directory

another way is to recursively go up from the current file until you hit

package.json

. cli should execute in

dendron-cli/lib/bin/cli.js

when bundled so you should be able to get to it by traversing we have a utility function to do that here -> https://github.com/dendronhq/dendron/blob/52145354331d1a9a84e55520550458762eba6df5/packages/common-server/src/filesv2.ts#L239

ua-parser-js-security-issue

adding-katex-options

Hey, is there a reference for the symbols used in the Lookup buttons? I'm talking about these:

iconOff: "chrome-maximize",
iconOn: "menu-selection",

The source is here: https://github.com/microsoft/vscode-codicons

Hi, team, how are You? Nice to meet you. I'm Felipe Janer, and today I'm starting my trial period as Senior Frontend Engineer. I hope we can work together and get to know the whole team. I'm excited to be part of this journey!

Regarding my onboarding process, and after reading the docs steps, I'm missing my Dendron private workspace. I'm taking a look at my inbox but didn't find any reference for it. Can you help me to get it, please?

Attaching the link for reference: https://handbook.dendron.so/notes/09a34445-345d-42c9-b82b-6f6691aed668.html#setting-up-your-workspace

Welcome Felipe! It's great to see the Dendron team grow! (And my puns are almost always intended 🌱)

Congrats on your new Position Felipe and nice to meet you 🙂

@User A new blog post has sprouted! 🌱 🔖 Dendron runs inside VSCode and VSCode-compatible editors (ex. VSCodium), so we always keep a close eye on updates. Our takeaways from the VSCode v1.61 include locked editor groups, doing the splits, and other notables that Dendronites may find interesting. https://blog.dendron.so/notes/83fIARBsKRnUlBL433RND/

I've been playing around with VSCode extensions and was starting on one that will do some of my own custom parsing of frontmatter to include in the content - given that only fm.title works right now. It does some basic substitution at the file content layer, but this really should be on the Preview. Are there any pointers on how to setup the extensions to run locally? I have DENDRON-PLUGIN workspace loaded and looking through ShowPreviewV2.ts, but I'm sure there's more involved than just hitting F5!

If you have the Dendron workspace, you can open the

dendron-main.code-workspace

file to load the workspace. Then you should have a "Run Extension: Local" entry in the run and debug menu. There should be some docs in the wiki, I'm AFK right now but I can link them later :)

Oh, and you'll want to first do

./bootstrap/bootstrap.sh

then

./bootstrap/watch.sh

to build everything & have your code changes load too

Okay here's the docs: https://wiki.dendron.so/notes/3489b652-cd0e-4ac8-a734-08094dc043eb/

Awesome, thanks! I had it running under the Extension: Local. I'm on WIndows - seeing the bash scripts - am I going to have to run under WSL to get a local debug session going?

I've gotten it to work with git bash too

Cool. Time to dive in!

Got the code all running, I can set breakpoints and step the code. But I cannot seem to find where the note is rendered for the webView. I'm thinking it's in

src\markdown\utils.ts

as

renderFromNote

or

renderFromNoteWithCustomBody

but I can't set breakpoints there (assuming it's the Engine and I need to run separately) and even making changes to the code seems to make no difference. Am I on the right track? Trying to add created and updated to the fm: object. It has just title at the moment). Using Preview V2 - assuming that's significant!

Ah, the note gets rendered in

dendronPub.ts

in combination with other

compile

functions for all markdown elements.