copyFiles() creates watcher on /tmp directory

[robertenk]

@symfony/webpack-encore v1.0.0 and @symfony/webpack-encore v0.32.0

When running in watch mode a watcher on the /tmp directory is created.
This only happens when using the .copyFiles() option.

I'm not sure if this is expected behavior - but in our case this is leading to problems.

As a workaround we added this config, which is solving the issue:

watchOptions: {
    ignored: ['/tmp', '**/node_modules']
}

[weaverryan]

Hmmm, we do use some hacking with .copyFiles() and create a file in /tmp and then require that file -

webpack-encore/lib/config-generator.js

Lines 185 to 224 in e6b11c9

	const tmpFileObject = tmp.fileSync();
	fs.writeFileSync(
	tmpFileObject.name,
	copyFilesConfigs.reduce((buffer, entry, index) => {
	const copyFrom = path.resolve(
	this.webpackConfig.getContext(),
	entry.from
	);
	let copyTo = entry.to;
	if (copyTo === null) {
	copyTo = this.webpackConfig.useVersioning ? '[path][name].[hash:8].[ext]' : '[path][name].[ext]';
	}
	const copyFilesLoaderPath = require.resolve('./webpack/copy-files-loader');
	const copyFilesLoaderConfig = `${copyFilesLoaderPath}?${JSON.stringify({
	// file-loader options
	context: entry.context ? path.resolve(this.webpackConfig.getContext(), entry.context) : copyFrom,
	name: copyTo,
	// custom copy-files-loader options
	// the patternSource is base64 encoded in case
	// it contains characters that don't work with
	// the "inline loader" syntax
	patternSource: Buffer.from(entry.pattern.source).toString('base64'),
	patternFlags: entry.pattern.flags,
	})}`;
	return buffer + `
	const context_${index} = require.context(
	'${stringEscaper(`!${copyFilesLoaderConfig}!${copyFrom}`)}',
	${!!entry.includeSubdirectories},
	${entry.pattern}
	);
	context_${index}.keys().forEach(context_${index});
	`;
	}, '')
	);
	entry[copyEntryTmpName] = tmpFileObject.name;

- specifically important are the 1st, 2nd and last highlighted line.

But I wouldn't think that would create a watcher on the entire directory... much like importing ./assets/foo/bar.js doesn't create a watcher on the entire assets/foo directory. I'm not doubting your report - more I'm saying that this is indeed mysterious, and I'm not sure why it's behaving like that...

[weaverryan]

... yea, I can't repeat this locally. I'm going straight to where the tmp file is being created - it's something crazy like /var/folders/ck/flmtvlh94bz_p8191nwkf1ph0000gn/T on my Mac - and am adding/modifying files in that directory, and watch is not rebuilding (it rebuilds if I actually modify the specific tmp file, of course).

It could be a Linux-specific thing?

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Hello? This issue is about to be closed if nobody replies.