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

Dependency Unhell #667

Open
Konard opened this issue May 25, 2023 · 1 comment
Open

Dependency Unhell #667

Konard opened this issue May 25, 2023 · 1 comment

Comments

@Konard
Copy link
Owner

Konard commented May 25, 2023

The project that just records real compatibility ranges between different libraries.

Let's start with NPM. We can get data about compatibility from package.json files. After that, we can collect feedback about compatibility from uses. Collect information about broken versions and so on.

The ultimate target is the ability to make complete update of all dependencies package.json with single command to the latest stable releases, that will most probably not fail. And if it fails, we can use that info to update compatibility ranges. So other users will not have the same problem. We also can make this process iterative if the package contains tests. If breaking changes are required, then we need another tool for that talks.

@Konard
Copy link
Owner Author

Konard commented May 26, 2023

https://www.npmjs.com/package/npm-check-updates

But it does not check for CommonJS/ESModule compatibility.
And it does not have information about complete package replacement like apollo-server to @apollo/server.

In any case it can be even better and for all package managers and languages.

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

No branches or pull requests

1 participant