Phillip Barta
Phillip Barta
Hey @blakeembrey, could you take a look at this and confirm if you're on board with the changes? Let me know if you have any concerns!
Hey @RobinTail, can you review again please? I implemented your suggestions.
Can we release this as a minor and recommend users to migrate away from `@types/finalhandler` to the built-in types, or would this require a major release?
@wesleytodd I understand your point. I thought about proposing [`pathe`](https://www.npmjs.com/package/pathe) which is used for example by Nuxt or [`unenv`](https://www.npmjs.com/package/unenv) but `content-disposition`s use case is so simple and only uses the...
Thanks for the feedback! > I think it is even supported there: [https://developers.cloudflare.com/workers/runtime-apis/nodejs/path/](https://developers.cloudflare.com/workers/runtime-apis/nodejs/path/) Just to clarify, `node:path` is only available in Cloudflare’s Workerd runtime when the `nodejs_compat` or `nodejs_compat_v2` flags...
@bjohansebas We have to options for the next release. Remove the emgines field and release v1.0.1 or publish v2
@UlisesGascon Has there been a decision from the TC?
CI Failure is unrelated to the change
@FrozenPandaz Sorry for pinging you directly but can we get this merged for v20?
> v23 is failing Please take a look at my comment