There's an esmodule branch which has this an as ES Module using import, but there is literally NO benefit to using this in that way.
It works with other ES Modules as-is.
Transforming it to an ES Module itself just breaks backwards compatibility with 99.999% of the npm ecosystem that uses Common JS.
There's an [`esmodule`](https://git.rootprojects.org/root/walk.js/src/branch/esmodule) branch which has this an as ES Module using import, but there is literally NO benefit to using this in that way.
It works with other ES Modules as-is.
Transforming it to an ES Module itself just breaks backwards compatibility with 99.999% of the npm ecosystem that uses Common JS.
There's an
esmodulebranch which has this an as ES Module using import, but there is literally NO benefit to using this in that way.It works with other ES Modules as-is.
Transforming it to an ES Module itself just breaks backwards compatibility with 99.999% of the npm ecosystem that uses Common JS.