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

Mark packages as deprecated and point to coral-xyz versions? #252

Open
mikemaccana opened this issue Jul 20, 2023 · 0 comments
Open

Mark packages as deprecated and point to coral-xyz versions? #252

mikemaccana opened this issue Jul 20, 2023 · 0 comments

Comments

@mikemaccana
Copy link

mikemaccana commented Jul 20, 2023

Using borsch as an example: there's quite a few downloads of the project-serum package but there's been no updates in quite a white, and project serum seems to have been replaced by openbook.

The coral equivalent is still actively maintained and popular.

The openbook equivalent is still actively maintained but few people are using it.

If the Serum packages are no longer maintained, they should be marked as deprecated

See https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions. For example:

npm deprecate @project-serum/borsh "This package is no longer actively maintained. Please use @coral-xyz/borsh instead"
@mikemaccana mikemaccana changed the title Mark packages as deprecated and point to openbook-dex versions? Mark packages as deprecated and point to coral-xyz versions? Jul 20, 2023
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