Change npm package scope to @hyperledger-labs #28
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
good-first-issue
Good for newcomers
Milestone
Received the recommendation on Rocket chat that we should publish under the labs scope when we are in the labs stage.
I raised the issue of migration effort and the answer was that it is acceptable to publish under multiple different names to save early adopters the headache.
Target new package scope:
@hyperledger-labs/blockchain-integration-framework
Once we graduate we can publish the same package under all these aliases in parallel if need be:
@hyperledger-labs/blockchain-integration-framework
@hyperledger/blockchain-integration-framework
and potentially of course whatever the final project name will end up being
@hyperledger/$FINAL_PROJECT_NAME
The text was updated successfully, but these errors were encountered: