-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
Using the same input and output does not work (always "Wrote 0 files") #1129
Comments
--output=.
The patch did not fix the bug. How to reproduce. I installed eleventy from github via npm -g and ran with above return and not Wrote 0 files. |
Hmm, I'm pretty sure this patch worked in my environment - from what I recall, I used the patched version to render my wedding website. Do the files write if you change the output directory to something else, eg. "build"? What is your operating system and Node version? |
@stuartpb Yes it does work if the folders are different. |
I'm not sure why that wouldn't work with the patch in #1133: that should evaluate to a check of What does |
@stuartpb Output:
|
You have to write three backticks around it ( |
Wouldn't that mean it's working? |
@stuartpb It wrote in in src/_site that time with setting of
What I need is not in src/_site but in src. |
Sounds like it used the default |
3 commands:
The second command outputs in src/_site based on .eleventy.js. Aside, I installed eleventy from git. |
Are you sure you get the same output for |
Don't ignore output paths that contain all input (fixes #1129)
Thanks! |
2022 still I cant solve this |
`animu5@animu5:~/Documents/GitHub/1bunnieabc-blog$ npm start
[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] Problem writing Eleventy templates: (more in DEBUG output) |
Describe the bug
The documentation states "Yes, you can use the same input and output directories, like so:
npx @11ty/eleventy --input=. --output=. --formats=md
"However, in practice, running that command always results in a
Wrote 0 files
result. Eleventy appears to be blacklisting its output directory from input matching, causing all attempts to output to the input directory (or any ancestor of the input directory) to match 0 files.See the output of the command when
DEBUG=Eleventy:EleventyFiles
is set:Note the
'!./**
(which matches the position of!./_site/**
when run with default options), effectively negating all of the preceding glob patterns.The text was updated successfully, but these errors were encountered: