Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retire project, and archive it. #6

Open
EvanCarroll opened this issue Oct 7, 2021 · 0 comments
Open

Retire project, and archive it. #6

EvanCarroll opened this issue Oct 7, 2021 · 0 comments

Comments

@EvanCarroll
Copy link

EvanCarroll commented Oct 7, 2021

This project is now confusing others and harming the ecosystem (you can see that here #1 ). I think it's time to retire it as a tool for a bad approach. I suggest saying this,

DEPRECATION NOTICE This project provides a wrapper for native functionality in node by bridging it to the XMLHttpRequest object that browser uses, allowing you to write just code using XMLHttpRequest in node and with TypeScript. This project further provides TypeScript definitions for that. This method of writing code for the client and server is deprecated: XMLHttpRequest has been replaced by the Fetch API: the Fetch API is standardized, and there are polyfills for older browsers that do not support it. The Fetch API is also available in Node. Write code for the Fetch API NOT XMLHttpRequest: there are methods of making it run everywhere, and it's more future safe.

Further, I would suggest archiving the project after the README is updated.

Note this is similar to the honorable approach that Request.js took. I suggest reading their rationale and following their footsteps to better the community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant