Skip to content
This repository has been archived by the owner on Apr 5, 2021. It is now read-only.

Migrating nodejs package to under @cityofzion namespace #109

Closed
rockacola opened this issue Dec 11, 2017 · 4 comments
Closed

Migrating nodejs package to under @cityofzion namespace #109

rockacola opened this issue Dec 11, 2017 · 4 comments

Comments

@rockacola
Copy link
Collaborator

Similar to @cityofzion/neon-js, we should be changing our NPM handle some point in the near future.

Current NPM handle:

Proposed namespaced handle:

  • @cityofzion/neo-js
@rockacola
Copy link
Collaborator Author

PR #113

@rockacola
Copy link
Collaborator Author

Postpone PR #113 and apply the migration onto master branch instead, as 0.5.1.

npm adduser
npm publish --access public

@rockacola
Copy link
Collaborator Author

rockacola commented Dec 31, 2017

neo-js is now available on new organization scope:

@rockacola
Copy link
Collaborator Author

@lllwvlvwlll I do not have access to neo-js-blockchain in NPM repository. Can you help me set deprecation notice for the old namespace.

  • perform npm publish from legacy/neo-js-blockchain branch
    • This should set the version to 0.5.2, which contains deprecation message on its README.md
    • Ignore 0.5.1 version number as it is polluted from my previous attempt.
  • Add deprecation message for anyone who still uses neo-js-blockchain package:
npm deprecate neo-js-blockchain@"< 0.6.0" "This package has been migrated! please update your package reference to @cityofzion/neo-js"

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

No branches or pull requests

1 participant