Also the workflow failed and this is the output on GitHub

@User do you have any thoughts what might be the issue here?

thanks for starting a thread, I really was feeling bad for hijacking the questions channel.

@User - do you have a

package.json

in your vault? see https://wiki.dendron.so/notes/FnK2ws6w1uaS1YzBUY3BR/#steps---setup-dendron

i don't have that file no. 😦

can you run the following commands locally in your workspace?

npm init -y 
npm install @dendronhq/dendron-cli@latest

Interesting. I definitely ran that command during the setup process. However running

npm init -y

seems to have generated a

package.json

file.

This output for the cli install command is ok?

Yeah, the npm audit is known to be broken. It warns about non-issues. The published Dendron sites are static, so there's no vulnerability.

So the workflow seems to have completed 🙂

🥳

YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSS

WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

Not going to lie i've physically stood up and cheered there

haha, achievement unlocked 🙂

As a quick aside before I stop bugging you guys i've just noticed that all of my images for both the published notes and my local notes no longer work.

The links do still go to images that are available though.

can you share the url to the site?

that note has a picture in it

![Goblin]()

and that's the full link in the markdown

(Which discord seems to have been able to embed :P)

Ah, looks like there's a bug where Dendron is applying the assets prefix to these images for some reason:

/epic-league/https://i.pinimg.com/originals/a2/c9/0d/a2c90dc72192c93114bcfd2c4e5e6923.jpg

Interesting. So it's doing that on the backend to Dendron itself then because it's also doing that from within VSCode aswell

yeah, this is a bug from our end. can you file a bug on github? i'll make sure we prioritize it!

Too easy. I'll report the other bug with the .next file not being added to the github-ignore list as well 🙂

Both have been added. Feel free to close this thread as all my issues have been either resolved or are now in the pipeline toward resolution. Thanks again MASSIVELY for being so awesome! 🙂