development instructions are here ->https://wiki.dendron.so/notes/PgwAXFfotfgpFVqHQRlBl.html

That’s surprising and excellent!

@User @User RFC for implementing full text search in Dendron's Next Publishing client -> https://wiki.dendron.so/notes/VaCraUDApW60xi0EDfBK9.html

I been stopped so far getting a running, debuggable instance of Dendron. So I went ahead and switched to https://github.com/microsoft/TypeScript-Website, which one, mostly likely is developed on windows machines, and secondly, ought to be a showcase of how do such things because, they should know. I think there is a lot to be learned from it, it has a lot of features that dendron could use already built in. It has a well thought out structure that we could borrow. It uses node for all its scripting, so no one would be locked out because they are on the wrong platform, plus the scripts are exposed within the vscode IDE. (control-shift-B, or, even better, open

NPM SCRIPTS

in the side bar). You can run those scripts via debug and follow and the warnings and errors. One final thing, I once suggested making DendronHQ into a Dev Container, and this monorepo, is one. Get this up and running took choosing

Clone this Dev Container

, when Vscode noticed it was one, running

yarn install

in the terminal, then running, (via debug), the

bootstrap

and

start

scripts. the website came up on

localhost:8000

, plus you get a quarriable GrapphQL ~ on another port. All under an MIT license.

@hikchoi since we were talking about electron apps… https://news.ycombinator.com/item?id=28465742

In

packages

, what's the difference between

dendron-next-server

and

nextjs-template

? What's each package for?

Ah, looks like

dendron-next-server

has UI components for the web interfaces in editor (like Preview V2) while

nextjs-template

has components for publishing.

yep, you got it. wrote some additional docs here (sync from dendron-site dev) * [[Web Components|pkg#web-components]] * [[Frontend Unification|dendron.dev.arch.wip#frontend-unification]]

Ok, I guess I finally got thinks figure out enough to get a next.js server setup and running, (trick was to follow the instructions in the wiki pages, but where ever their was something to run on the command line, find the similarly named script under the

NPM-SCRIPTS

, and hit its

run

button. After a few prerequisite scripts, the

start

tool/script/task under

packages/dendron-next-serv...

opened a browser window on relevant port. However, the is no nav pane or notes,

I think you are missing the workspace data files. There's a link to a sample in the docs, or you can also export from your own workspace using the dendron command line.

This is despite "curling-in" the dendron.so zip file, (which, doesn't look right actually, a lot of empty, named files

Try exporting from your own workspace, I used that and it seemed to work. I'll check if the zip file is broken later today.

Ok, thanks

Has anyone ran into the issue of breakpoints not taking hold while trying to debug core plugin with message on breakpoint in VSCode while hovering "unbound breakpoint"?

I've had that happen to me as well. Didn't dig into it too much but something about the source not mapping to the compiled files.

if you’re not debugging the plug-in code directly, you’ll want to drop a debugger statement in the code

see https://wiki.dendron.so/notes/yhpcSlIpwsBX2iHjfyutP.html

running local next.js preview from command line, getting this on localhost:

There is no data folder in '.next'

frames expanded:

from console:

Error: C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\data\notes.json: ENOENT: no such file or directory, open 'C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\data\notes.json'
    at Object.openSync (node:fs:505:3)
    at Object.readFileSync (node:fs:401:35)
    at Object.readFileSync (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\jsonfile\index.js:50:22)
    at getNotes (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\.next\server\pages\index.js:255:68)
    at getStaticProps (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\.next\server\pages\index.js:188:70)
    at renderToHTML (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\next\dist\next-server\server\render.js:28:1695)
    at async C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\next\dist\next-server\server\next-server.js:111:97
    at async __wrapper (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\next\dist\lib\coalesced-function.js:1:330)
    at async DevServer.renderToHTMLWithComponents (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\next\dist\next-server\server\next-server.js:136:387)
    at async DevServer.renderToHTML (C:\VC\git\Dendron-Notebanks\Bank.Markdown\vault\.next\node_modules\next\dist\next-server\server\next-server.js:137:610) {
  errno: -4058,
  syscall: 'open',
  path: 'C:\\VC\\git\\Dendron-Notebanks\\Bank.Markdown\\vault\\.next\\data\\notes.json'
}

did you add the sample data? see https://wiki.dendron.so/notes/PgwAXFfotfgpFVqHQRlBl.html#run

Yeah, must have missed this prerequisite😋 . From running various command,

.next

folders were scattered all over, moved contents in to their

/vault/.next/

position, and it's working now. It is next.js generated, it has the same hiccups as V2 preview, (no svg images, no table borders). thx

yeah, those items are still on the backlog 😅 currently have a #crop vote for the table borders issue

@User @User For folks working on Dendron Lookup logic, created a state diagram showing different transitions since it's gotten a bit involved (NOTE: the mermaid size is a bit off on the diagram - will be fixing this soon!) https://wiki.dendron.so/notes/PZ3IzgdeZBbFRvalzI9fp.html

Has there been any thought into frontmatter namespacing? If markdown file interop is a value (the reason markdown was chosen, if I remember correctly), seems a few different apps are stomping on the same frontmatter values.

(I use logseq for daily bullet journaling, and just noticed that our frontmatter breaks it ... filing a report over there too.)

there have been many thoughts, in different stages of completeness. what is the issue with logseq that you're seeing?

title

generated by Dendron creates all sorts of strange behavior in the Journal view in Logseq (which should be fixed there), but had me wondering if something like

dendron:title

was a good idea, or how people namespace in Frontmatter generally.

got it. yeah, we haven't done anything with namespaces at the present. there's been an idea of making it configurable but its quite far in the backlog at this point