Closed JustinBeckwith closed 5 years ago
Use the v0.8 branch
It looks like there's a lot going on in there! If I may suggest - it's probably a lot easier to make many of these changes on master and cut a breaking release. The big issue we're running into is that many of your dependencies are out of date, which makes installation trigger all kind of audit alerts. I'd be happy to help contribute if that's helpful! I'd much rather help make this shine than fork.
The v0.8.0 branch is much needed for international URLs, so a breaking change is will happen anyway.
Node.js 4 and down are all out of LTS, so you probably don't need to support those :) Any thoughts on a PR to update supported versions and drop these?