Wes Todd
Thanks @commonbreed. Can you explain what you mean by "TS port"? > It's likely that the "outdated" types are still accurate > whether any signatures have changed from 4.16.1 to...
> dougwilson has prohibited porting this code base to TypeScript Doug is not a dictator. He and the rest of the contributors do not want to port anything to TS....
> I'm fully aware this is a community project and never supposed Doug I was not admonishing you, just making sure the governance model was clear to everyone who might...
I updated that in the module, and assuming it will move into the express family somewhere I used the tilde in here.
Anything blocking us from moving forward? Do we need to move the repo or can it live where it is?
Is there something I can do on this PR to move it forward?
Awesome!! I will go through and do a rebase/cleanup pass asap.
Yeah I can cap that for sure. For the back porting, I think we can do it, just need to call into the new stuff and log the deprecation in...
Ok, so the changes in `4.x` are so different that it will actually be better for me to make two separate PR's. Other than the examples, basically every line changed...
Ok, #3714 is open. It ports all these changes to 4.0 and provides deprecation warnings. Once we figure out the points I brought up over there I will finalize the...