Currently only JSON files will work (for preview, code intellisense and exports) in VSCode. If you want to use js config files, you have to use @argdown/cli. It seems like VSCode does not allow extensions to require Javascript modules with absolute paths. I asked for confirmation on this on stackoverflow.
The main downside of this is that without this it is impossible to add custom plugins to the VScode parser in the VSCode extension and the VSCode language server.
This was another problem from webpack bundling hell. I posted the solution on stackoverflow and opened an issue at import-fresh. Will be fixed in next release.
Currently only JSON files will work (for preview, code intellisense and exports) in VSCode. If you want to use js config files, you have to use
@argdown/cli
. It seems like VSCode does not allow extensions to require Javascript modules with absolute paths. I asked for confirmation on this on stackoverflow.The main downside of this is that without this it is impossible to add custom plugins to the VScode parser in the VSCode extension and the VSCode language server.