Jon Ursenbach

Confirmed that the work in v29 resolves this for us on a `module` and `moduleResolution` of `node16`. Thanks @ahnpnl!

Any updates on this? It's starting to cause some downstream issues with packages that depend on v6 of the parser. ``` > npm ci npm ERR! code ERESOLVE npm ERR!...

fwiw, iirc last time i looked into that you still needed to pass the `--experimental` flag to Node for ESM in order to run `bin/rdme`. That was like a year...

Now that we've got `rdme guides` and `rdme guides:prune` aliased to `rdme docs:` can we deprecate and remove `rdme docs`?

For dumping `node-fetch` and `formdata-node` for native `fetch` the place where you're using `formdata-node` in https://github.com/readmeio/rdme/pull/856 can be replaced with this diff: ```diff diff --git a/src/lib/streamSpecToRegistry.ts b/src/lib/streamSpecToRegistry.ts index a73445f..9d4f68a 100644...

Hi, I work here at @vimeo, and we'd recommend you not use this library as it uses our old Advanced API that's currently EOL'd. Unfortunately though, we don't have any...

@marcamillion Aside from all new endpoints, a lack of XML support, our new API is built on OAuth 2. It might be possible to fork and update this library, but...

@bo-oz Basically everything has changed. We're (@dashron actually) still working on our Advanced API to API 3 conversion guide, which will make everything a lot clearer. I can't give a...

Might also be worth extending this to all instances where you'd reference a representation (`@api-return`, `@api-throws`, and possibly `@api-warning` (#70).

Doing this'll also help us to remove our dependency on PHP namespacing. https://github.com/vimeo/mill/issues/17