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
I can’t seem to make WebC files use permalink to output files to a different location. You can checkout the sample barebone project or use these steps to reproduce.
upd: Ouch, this is probably an issue for the eleventy-plugin-webc, please move it
Steps to reproduce
1. Set up a sample project:
mkdir webc-permalink
cd webc-permalink
npm init -y
npm i --save-dev @11ty/eleventy@v2.0.0-canary.31 @11ty/eleventy-plugin-webc
2. Create eleventy.config.js with the following content:
I think we’ll change the failure case here to return the raw content. Right now we attempt to evaluate the permalink as JavaScript—but it just throws an error if that fails. I’d like to change that to be more straightforward/friendly in WebC v0.9.0.
I can’t seem to make WebC files use
permalink
to output files to a different location. You can checkout the sample barebone project or use these steps to reproduce.upd: Ouch, this is probably an issue for the eleventy-plugin-webc, please move it
Steps to reproduce
1. Set up a sample project:
2. Create
eleventy.config.js
with the following content:3. Create
page.liquid
with the following content4. Run
npx @11ty/eleventy
5. Rename
page.liquid
topage.webc
6. Run
npx @11ty/eleventy
Expected behavior
File
_site/index.html
on steps 4 and 6Actual behavior
Error on step 6: Cannot read properties of undefined (reading 'html')
Full error output
The text was updated successfully, but these errors were encountered: