You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When opening the preview, a warning occurs: Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency. While the preview still works, this is very annoying.
To Reproduce
Steps to reproduce the behavior:
Install the plugin.
Set let g:mkdp_auto_start = 1. (didn't test if it still occurs when this variable is 0)
Open a Markdown document.
Expected behavior
Preview works without warning prompt.
Environment:
OS: Manjaro KDE (2021.05.07)
Nodejs: v16.0.0
npm: 7.12.0
yarn: 1.22.10
Possible solution/workaround:
Run cd app && yarn upgrade after installation.
The reason seems to be an old version of package winston, which is required by package neovim. See winston#1797. A simple cd app && yarn upgrade get me on the way.
Since I'm not familiar with nodejs programming, I'm not sure whether this is an elegant solution. Hoping anyone provide a final solution and commit it. Thanks!
The text was updated successfully, but these errors were encountered:
Describe the bug
When opening the preview, a warning occurs:
Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
. While the preview still works, this is very annoying.To Reproduce
Steps to reproduce the behavior:
let g:mkdp_auto_start = 1
. (didn't test if it still occurs when this variable is 0)Expected behavior
Preview works without warning prompt.
Environment:
Possible solution/workaround:
cd app && yarn upgrade
after installation.The reason seems to be an old version of package
winston
, which is required by packageneovim
. See winston#1797. A simplecd app && yarn upgrade
get me on the way.Since I'm not familiar with nodejs programming, I'm not sure whether this is an elegant solution. Hoping anyone provide a final solution and commit it. Thanks!
The text was updated successfully, but these errors were encountered: