-
-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.markdown
files not processed from custom extension alias (v3.0.0-alpha.11 and above)
#3337
Comments
(Am just seeing if I can update my build so that it works if the required env variables are not present…) |
Have updated my repo such that if the env variables are not present, the site will still build. Interestingly, even more files (~89%) do not get written in this case:
|
Investigating… |
This is almost certainly #3302 |
I think it’ll be fixed with an
but I haven’t confirmed in your project yet (I’m seeing some other duplicate permalink issues that might be from missing environment variables) |
Ahhh, okay, that makes sense – something to add to the upgrade docs/plugin! I’m getting the duplicate permalinks error now too, and that’s with the environment variables set. Will dig into it, but this wasn’t reported as an error before – might have this been silently erroring until this point? |
That might be a mistake—I did some changes in that code recently for #3327 I might’ve missed something there. That was shipped in It doesn’t look like you were using |
markdown
files not processed from custom extension alias (v3.0.0-alpha.11 and above)
markdown
files not processed from custom extension alias (v3.0.0-alpha.11 and above).markdown
files not processed from custom extension alias (v3.0.0-alpha.11 and above)
If it helps, I get |
Using the uncommon-but-Gruber-preferred |
After fixing #3339, I see a new conflict that I’ll have to dive into tomorrow, nothing is jumping out at me yet:
|
That one may very well be time zone dependent; I’ll let you know once |
oh—oh no! that’s probably it. Not sure the best way to fix that globally but the brand new #867 (comment) will probably give you an escape hatch, if you’re interested. |
Oooh, that might be just the ticket, thanks! |
https://github.com/11ty/eleventy/releases/tag/v3.0.0-alpha.15 is now available—going to consider this one resolved unless I hear otherwise, thank you! |
Operating system
macOS Sonoma 14.5
Eleventy
v3.0.0-alpha.11+
Describe the bug
Using any version of
v3.0.0-alpha
afteralpha.10
results in 80% of files no longer being written to disk:Copied 2046 files / Wrote 2647 files in 8.08 seconds (3.1ms each, v3.0.0-alpha.10)
Copied 2046 files / Wrote 556 files in 2.59 seconds (4.7ms each, v3.0.0-alpha.11)
I thought this might be an issue with incremental builds, but running
eleventy
without any flags gives the same result. 🤷🏼Reproduction steps
npm i
npm start
Reproduction URL
https://github.com/paulrobertlloyd/paulrobertlloyd-v4
The text was updated successfully, but these errors were encountered: