You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been building some stuff with 2.0, and its a bit of a pain having to check if each of the libs i want to use (for ex, spl-token, metaplex, etc) have already made a 2.0 compatible library. It would be good imo to maintain this list, somewhere easily accessible to at a glance check if the libs you need are ready.
Example use case
Ex: I'm starting a new project, and see 2.0 has been released, and i want to be up-to-date with the latest tech - but i also don't want to reinvent the wheel for every lib i need to use.
Having a quick list to see which libs are 2.0 compatible will help inform my decision of which version to go with.
Details
It kinda reminds me of areweturboyet - we probably dont need something quite this complex, i imagine even something as simple as a readme with the most commonly used packages and either a ✅ or ❌, as well as a link to the lib
The text was updated successfully, but these errors were encountered:
Motivation
Been building some stuff with 2.0, and its a bit of a pain having to check if each of the libs i want to use (for ex, spl-token, metaplex, etc) have already made a 2.0 compatible library. It would be good imo to maintain this list, somewhere easily accessible to at a glance check if the libs you need are ready.
Example use case
Ex: I'm starting a new project, and see 2.0 has been released, and i want to be up-to-date with the latest tech - but i also don't want to reinvent the wheel for every lib i need to use.
Having a quick list to see which libs are 2.0 compatible will help inform my decision of which version to go with.
Details
It kinda reminds me of areweturboyet - we probably dont need something quite this complex, i imagine even something as simple as a readme with the most commonly used packages and either a ✅ or ❌, as well as a link to the lib
The text was updated successfully, but these errors were encountered: