Dustin Van Tate Testa

Also I feel like this is a more substantial breaking change an have no idea when it occured between v99.0.0 and v109.0.0... really I feel like this semver sysytem isn't...

the native's version is not v109.0.0 it's version_109

Just the 2 wasted subversions... Regardless, this is besides the point of breaking module compatibility. You can look at yargs for example of a package which supports both esm and...

@thornjad it's been over a month,,,;.;

Maintainer is asking for funding but hasn't touched this repo all summer (~3 months)

It seems that this PR is now only needed to support nodejs v18.0.0 - v18.4.0 as they've reverted the change. Would update the version numberrs in the pr. 


There are several open pull requests which fix this which have been open for several months now but the maintainer for this repo ( @thornjad ) seems to be ignoring...

Could probably just use the same logic that's in `planning/demo.ts` for a test suite https://github.com/dvtate/postfix-haskell/blob/master/planning/demo.ts

@digitarald It seems that marking an extension as "deprecated" makes it impossible to install in vscode. I would consider renaming this feature. The microsoft provided extension makes my VM freeze...