Config file resolution fails on Windows about lws HOT 4 CLOSED

yeah, the big institutions are often the furthest behind.. I realise v12 is still maintained, the main reason i moved support to minimum v14 was because the codebase is now ECMAScript with a package.json that uses the exports feature.. v12 supports ESM but behind a flag (until recently I believe - i think the flag requirement was removed in v12.20, will need to check).. I also had an issue with the CommonJs build of lws failing in v12 (the build produced by rollup didn't support dynamic loads, required by plugin-loading features like --view and --stack)..

If you have any general feedback in the future, feel free to post in the discussions tab..

from lws.

Was a good point about the slow-moving institutions, so support extended back to v12.20

from lws.

Fixed by your PR #19. Thanks!

Since you already require a pretty modern Node

Node versions prior to v14 are no longer active..

from lws.

Wow, that's fast turnaround 😄

Per the release schedule, Node 12 LTS is still in Maintenance and doesn't hit EOL until April of next year. Node 14 is only a year old -- venerable in the fast-moving world of JS, but a relative baby in terms of corporate IT. (I work with government, and a lot of the tech is, uh, not new.)

from lws.