Bug: config dependencies changes don’t apply during serve/watch

[dwkns]

Consider:

// eleventy.config.js
const data = require("./data.js");
module.exports = (eleventyConfig) => {
  console.log(`[ data ]:`, data); // equivalent of doing something with the data
 
  return {
    dir: {
      input: "src",
      output: "dist",
      layouts: "_layouts",
      data: "_data",
    },
  };
};

And

// data.js
module.exports = "this is a test";

It is super annoying that every time you make a change in data.js you have to:

• Restart the dev server; or
• Also make a change in eleventy.config.js
  If you don't then eleventy.config.js doesn't see the change in the dependent file (data.js)

Ideally you'd be able to add something like:

eleventyConfig.setServerOptions({
...
alwaysProcess: [ 'eleventy.config.js', 'some-other-dependency.js']
});

It would certainly make plugin development a lot easier.

Thoughts?

[bobmonsour]

There appears to be a "watch" option on the dev server where you can specify an array of files to watch which will trigger a server update. See here:

https://www.11ty.dev/docs/dev-server/#options

[zachleat]

This should happen automatically in Eleventy. We’ve fixed a few bugs on this recently, what’s the newest version you’ve tested on?

[zachleat]

https://github.com/11ty/eleventy/issues?q=label%3A%22bug%3A+--serve+restart%22+is%3Aclosed might be a good start to look at dupes

[dwkns]

Tested on 2.0.0
Minimal repo to reproduce here:
https://github.com/dwkns/eleventy-issue-2864

I saw this issue which suggests you've made changes for 2.0.1, but I'm not sure how I can test against that.

[zachleat]

I was able to reproduce this on 2.0.0 and can confirm that 2.0.1 fixes it!