-
-
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
addWatchTarget ignored when used in a custom config file #1448
Comments
Confirmed. |
Has this been fixed? |
Still not fixed and pretty annoying! Any trouble with #1568 from @dafiulh ? |
* feat: improve sass compilation process * fix: use default config file name until 11ty/eleventy#1448 is fixed
OMG, thanks for this. Needs fix or note. |
Any updates on this? Looks like this PR adds a fix for this issue? |
Confirmed this as already fixed (tested in 2.x and 1.x) As for the PR #1568 I was able to confirm that this issue is no longer relevant on 1.x:
// eleventy.config.js
module.exports = function(eleventyConfig) {
eleventyConfig.addWatchTarget("assets/**");
}; Thanks everyone! (please speak up if I’m wrong!) |
Hi,
When used in a custom config file,
addWatchTarget
is ignored.To Reproduce
Steps to reproduce the behavior:
It's nothing more than Eleventy's Getting started with 2 config files:
.eleventy.js
andconfig/eleventy.js
. Both contain a call toaddWatchTarget
.DEBUG=Eleventy npx @11ty/eleventy --serve
.addWatchTarget
works:.eleventy.js
:mv .eleventy.js ._eleventy.js
DEBUG=Eleventy npx @11ty/eleventy --config=config/eleventy.js --serve
addWatchTarget
is broken:Expected behavior
addWatchTarget
should work when called from a custom config file.As a bonus, should
.eleventy.js
even be loaded when Eleventy is called with a custom config file ?The text was updated successfully, but these errors were encountered: