Node version(node -v: Should be at least nodejs 6.9. If not, please update before posting an issue!): v10.15.1
Your site _config.yml (Optional):
Your theme _config.yml (Optional): yalia
Hexo and Plugin version(npm ls --depth 0):
Your package.json package.json:
markdown allows the table that adds a indentation, but this table displays unsuccessfully on website after executing hexo deploy command。
For example:

Display on website:

How should I solve this problem?
@kwilove
Because "4 spaces" means code block at a markdown specification.
Please see below.
Thanks :)
@YoshinoriN
Thanks for your reply!
But i have a new question.
Use the same markdown text:

And then i open directly previous markdown file by browser, it will displays:

Why does it work on browser successfully? Do you know why the results were different?
thanks!
@kwilove
Do you use a something extension to a browser?
My understanding, a browser cannot be rendering a markdown to HTML.
@YoshinoriN
Yes, you are right.
I using a IDE called "Visual Studio Code" to write a markdown file, and the IDE has installed a plugin "Markdown Preview Enhanced", is this the cause?
@kwilove
OK. I got it. It is not VSCode plugins problem. Do you using hexo-renderer-marked?
hexo-renderer-marked is depended on marked. It seems fixed in markd #1446 and it's released in v0.6.2
Please see below demo.
We already bump to marked 0.6.x at hexo-renderer-marked v1.0.0
Would you please try to update your hexo-renderer-marked to 1.0.1?
Please be careful it has some breaking changes.
Below is dependency about hexo-renderer-marked 1.0.1
C:\Users\N.Yoshinori\tmp\marked-test
`-- [email protected]
+-- [email protected]
| +-- [email protected]
| +-- [email protected]
| | +-- [email protected]
| | | `-- [email protected]
| | `-- [email protected]
| +-- [email protected]
| | +-- [email protected]
| | | +-- [email protected]
| | | `-- [email protected]
| | `-- [email protected]
| | `-- [email protected]
| +-- [email protected]
| +-- [email protected]
| `-- [email protected]
+-- [email protected]
`-- [email protected]
I'm so sorry to wrong answer when first time...
@YoshinoriN
Well,i will try it,thanks.
This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
@kwilove
OK. I got it. It is not VSCode plugins problem. Do you using hexo-renderer-marked?
hexo-renderer-marked is depended on marked. It seems fixed in markd #1446 and it's released in v0.6.2
Please see below demo.
We already bump to marked 0.6.x at hexo-renderer-marked v1.0.0
Would you please try to update your hexo-renderer-marked to 1.0.1?
Please be careful it has some breaking changes.
Below is dependency about hexo-renderer-marked 1.0.1
I'm so sorry to wrong answer when first time...