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.

Sign up for GitHub

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

Jump to bottom

Migrate to @extend-chrome #3

Closed
jacksteamdev opened this issue Jun 8, 2020 · 1 comment
Closed

Migrate to @extend-chrome #3

jacksteamdev opened this issue Jun 8, 2020 · 1 comment
Assignees
@jacksteamdev

Comments

@jacksteamdev
Copy link
Contributor

We're migrating this library over to a new and more aptly named organization: extend-chrome!

TODO

  1. Catalog bumble-org dependencies
  2. Update README.md
  3. Update package.json
  4. Transfer GitHub repo
  5. Transfer NPM package
@jacksteamdev jacksteamdev self-assigned this Jun 8, 2020
@jacksteamdev jacksteamdev added this to To do in Migrate to @extend-chrome via automation Jun 8, 2020
@jacksteamdev jacksteamdev moved this from To do to In progress in Migrate to @extend-chrome Jun 9, 2020
@jacksteamdev
Copy link
Contributor Author

Reached out to the package owner of the npm package jest-chrome on Twitter just now. This might be a better option than @extend-chrome/jest-chrome.

We should think of @extend-chrome as a verb: @extend-chrome/storage, @extend-chrome/messages. Those libraries extend/wrap the Chrome API, so it's intuitive to name them that.

Migrate to @extend-chrome automation moved this from In progress to Done Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacksteamdev jacksteamdev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacksteamdev