corrupted output dir with addPassthroughCopy while --serve --incremental running

[Gr0t3Man]

I have a ‘assest’ directory with multiple sub folders, which are configured with a addPassthroughCopy command;

eleventyConfig.addPassthroughCopy({ "assets/styles": "styles" });
eleventyConfig.addPassthroughCopy({ "assets/scripts": "scripts" });
eleventyConfig.addPassthroughCopy({ "assets/root": "/" });
eleventyConfig.addPassthroughCopy({ "assets/images": "images" });

When eleventy is running in –-serve --incremental mode and a jpg file is added to the ‘assets/images’ dir, eleventy sees that the file is added.

In the _site directory a file with the name ‘images’ is created!!?? The preview of this file shows the actual picture which was added. The directory _site/images isn’t available anymore.

After this i must stop eleventy, delete the corrupted file and restart eleventy to regenerate the missing directory.

Currently I’am running v1.0.0, but I saw this problem first in the last days of December, when I was running the latetst beta version of that time.

When only running the --serve mode, the files are nicely added/changed in the output directory.

Note: when I edit/add a file in the ‘assets/root’ folder, the entire _site directory is corrupted!!

Environment:

• MacOS Mojav 10.14.6
• Eleventy Version v.1.0.0

Additional context
Add any other context about the problem here.

[bennypowers]

Same here.

eleventy --serve --incremental --config=.eleventy.cjs

eleventyConfig.addPassthroughCopy('docs/bundle.{js,map,ts}');
eleventyConfig.addPassthroughCopy('docs/demo.{js,map,ts}');
eleventyConfig.addPassthroughCopy('docs/main.mjs');
eleventyConfig.addPassthroughCopy('brand/**/*');

const repoRoot = join(__dirname, '..', '..');

// Copy all component and core files to _site
const files = Object.fromEntries([
  ...fs.readdirSync(join(repoRoot, 'elements')).map(dir => [
    `elements/${dir}`,
    `components/${dir.replace('pfe-', '')}`,
  ]),
  ...fs.readdirSync(join(repoRoot, 'core')).map(dir => [
    `core/${dir}`,
    `core/${dir.replace('pfe-', '')}`,
  ]),
]);

eleventyConfig.addPassthroughCopy(files);

The files object ends up looking like this:

{
  'elements/pfe-accordion': 'components/accordion',
  'elements/pfe-autocomplete': 'components/autocomplete',
  'elements/pfe-etc': 'components/etc',

  'core/pfe-core': 'core/core',
  'core/pfe-sass': 'core/sass',
  'core/pfe-styles': 'core/styles'
}

First run is fine, _site/core/core is a directory full of files.

Then, if I save core/some/thing.ts, after the build, I notice that _site/core/core is no longer a directory, but a file, and it's text contents are identical to core/some/thing.ts

[binyamin]

Confirmed on linux. Related #108

[Gr0t3Man]

Solved in with Eleventy 1.0.1 and 2.0.0-canary.4.
See #2278

[stormitornado]

it's still has such bug (version 2.0.1)
I wrote this to copy everything from public to the root, at first time it copied properly with the same folder structure, but on update this structure brokes, files go directly to the root.
eleventyConfig.addPassthroughCopy({"public": "/"});
Maybe I should write another rule?