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
The solution uses this plugin, but one of the MD does reference an image from the assets, so relatively from root, via: /assets/img/wrong-way.jpg
This makes the build fail, du to the plugin:
`Error` was thrown:
Error: [Eleventy-Plugin-Page-Assets] Cannot resolve asset "/assets/img/wrong-way.jpg" in "_site/posts/DDD Series - 2 - The history of DDD/index.html" from template "./src/posts/programming/2021-01-05-ddd-series/02/index.md"!
at C:\$_Work\11ty-custom\node_modules\eleventy-plugin-page-assets\src\plugin.js:80:21
It also results in the MD file not being translated to HTML.
FR: please add support to use images relative to root (starting with /)
BUG: probably a try/catch around the plugin logic would be desirable, so that at least the HTML content gets properly generated (even with a broken IMG link) - still better than having nothing
NOTE: IMO after the const / let issue (see PR fix variable assignment error #2) using directory mode would be probably the best way to approach extra content along the posts (MD files)
Additionally: when using permalinks post/{title} and fixing the const / let issue in the plugin and using any img copy over, I end up with a weird structure:
The entire source is attached to play with (debug)...
The text was updated successfully, but these errors were encountered:
The solution uses this plugin, but one of the MD does reference an image from the assets, so relatively from root, via: /assets/img/wrong-way.jpg
This makes the build fail, du to the plugin:
It also results in the MD file not being translated to HTML.
11ty-custom.zip
Additionally: when using permalinks post/{title} and fixing the const / let issue in the plugin and using any img copy over, I end up with a weird structure:
The entire source is attached to play with (debug)...
The text was updated successfully, but these errors were encountered: