Investigate dependencies of 11ty

[43081j]

https://github.com/11ty/eleventy/blob/main/package.json

Zach seems happy to do some maintenance here, so we should take a look.

Obvious ones:

• rimraf (already done)
• fast-glob, is-glob, etc (replace with tinyglobby)
• chokidar (part of Update chokidar to @4 #138 )
• ava (big change - but vitest would be better)

We are going to track this in an equivalent umbrella issue inside the eleventy repo. So do not make individual issues unless Zach decides to pull one out of the umbrella to focus on.

[pralkarz]

• graceful-fs can most likely be replaced with node:fs in modern versions. Depends on how they're using it though.
• micromatch -> picomatch for deduping with tinyglobby
• p-map -> should probably be inlined

[Krinkle]

chokidar

You may want to consider switching to node-watch by @yuanchuan. I did this for QUnit back in 2018 and it helped us reduce dependencies from 142 to 9.

https://qunitjs.com/blog/2019/01/06/qunit-2-9-0/

qunitjs/qunit#1342 (comment)

Before: QUnit 2.8.0 has 142 dependencies.

After: QUnit 2.9.1 has 9 dependencies.

Before	After

Pull request: qunitjs/qunit#1345

[Fuzzyma]

@Krinkle what is the advantage over choking v4? It doesn't seem to support globs only filters. And filters don't cut it when watching directories because they will filter out subdirs that don't match the glob (even tho they could have files that do match the glob)

[43081j]

Note that chokidar currently has 1 dependency. Times have changed since you switched 👀

I'm biased since I maintain it but I would just stick with it and benefit from the de-dupe

[Krinkle]

what is the advantage over [chokidar] v4? It doesn't seem to support globs only filters. And filters don't cut it when watching directories because they will filter out subdirs that don't match the glob (even tho they could have files that do match the glob)

@Fuzzyma Filtering out one result and recursively skipping an entire directory, are two different things. I haven't tried it recently, but the readme sounds like Chokidar made the same decision as node-watch. https://github.com/paulmillr/chokidar/tree/4.0.3 reads:

v4 is out! It […] removes support for globs, […]

... except node-watch does still support the optmization to skip subtrees when desired. This becomes less relevant over time, but it's there today.

Note that chokidar currently has 1 dependency. Times have changed since you switched […]

@43081j I'm glad Chokidar was able to make such a drastic change. That benefits a huge portion of the ecosystem. Very nice!

Ultimately, I suppose the key question for this issue is: What does Eleventy actually need?

[Fuzzyma]

Chokidar v4 also allows filtering via ignore and it will filter out any subtree you want.

However, this is unfortunately not a replacement for globs as i experienced painfully.

Not shooting against node-watch here. Just wanted to make sure that the capabilities are understood :)

// Edit: actually looked at the docs now and it seems that node-watch allows to skip items more granualy than chokidar by returning false / "skip"

[43081j]

Let's find out what 11ty currently uses chokidar for and go from there

There's still opportunity to add new functionality to chokidar but I suspect 11ty won't need that

[43081j]

also note 11ty/eleventy#3360 so nobody duplicates that work (rimraf was also removed recently from recursive-copy)

[outslept]

11ty/eleventy#3715 👀

[zachleat]

Shipped both of these PRs: https://github.com/11ty/eleventy/releases/tag/v3.1.0-alpha.1

They’ll roll up with v3.1.0 stable!

[43081j]

awesome, thanks for updating us @zachleat

if there's more to be done, it'd be nice to get things moving again on this.

e.g. there's 2 dependencies to generate slugs, maybe we can unify down to one

edit: seems you deprecated slug filter already. maybe we can remove that one day? 👀

[outslept]

What about those ones?

1. @eslint/eslintrc - given the simplicity of the configuration, we can simply shave it off and use the modern flat config approach directly

2. cross-env — after searching through the main repo, I couldn't find any actual usage; looks like it's safe to remove.

3. marked — I noticed that marked is only used in test files; if its usage is not critical, it might be possible (assuming API compatibility) to migrate these test cases to markdown-it and remove marked as a dependency altogether.
4. minimist — possibly could be replaced with mri

[43081j]

1. good shout, both plugins ship flat configs now I think (eslint and prettier). it'd be a good clean up for maintainers at least
2. maybe this suggests we should add knip to the repo if it hasn't been already, to detect unused dependencies
3. since its a dev dependency, it probably doesn't matter much but would improve install time for maintainers
4. good idea, would be interested in seeing if this is an easy move

in particular, 1 and 4 seem like easy wins. maybe if you want to have a stab at them, open a draft PR for each and we can help you out?

[outslept]

[eleventy-img]

• #292: Removing @eslint/eslintrc

---

[eleventy-dev-server]

• #110: minimist → mri (intentionally keeping as draft)

---

[eleventy-import]

• #15: graceful-fs → node:fs

---

[eleventy-plugin-template-languages]

• #19: Flat config migration & remove @eslint/eslintrc

---

[eleventy-fetch]

• #63: graceful-fs → node:fs

---

[eleventy]

• #3758: Remove @eslint/eslintrc & cross-env
• Separate PR for minimist → mri (planned)

---

[outslept]

2. maybe this suggests we should add knip to the repo if it hasn't been already, to detect unused dependencies

I think at first, if Zach is willing, he can try to use this module globally installed and then it can be integrated as a dev dependency

[zachleat]

Pending here, with a few initial suggestions from the tool: 11ty/eleventy#3757