Skip to content
This repository was archived by the owner on Apr 22, 2026. It is now read-only.

chore: replace blockstack libs with stacks lib, remove pkg keychain - #743

Closed
friedger wants to merge 2 commits into
leather-io:release/connect-2from
friedger:chore/remove_blockstack
Closed

chore: replace blockstack libs with stacks lib, remove pkg keychain#743
friedger wants to merge 2 commits into
leather-io:release/connect-2from
friedger:chore/remove_blockstack

Conversation

@friedger

@friedger friedger commented Jan 7, 2021

Copy link
Copy Markdown
Contributor

Description

As a developer, I don't want to replace blockstack.js with stacks.js to later learn that I need blockstack.js for @stacks/connect.

This PR

  • replaces imports of blockstack with the corresponding libs of stacks.js
  • removes keychain package

Type of Change

  • New feature
  • Bug fix
  • API reference/documentation update
  • Other

Does this introduce a breaking change?

Developers can remove blockstack as a peer deps from their apps.

Are documentation updates required?

No

Checklist

@friedger friedger mentioned this pull request Jan 7, 2021
5 tasks
@friedger

friedger commented Jan 7, 2021

Copy link
Copy Markdown
Contributor Author

Should be part of https://github.com/blockstack/ux/milestone/30 as it replaces #686

@kyranjamie

Copy link
Copy Markdown
Contributor

Hmm what's going on with CI, I've not see Error: Resource not accessible by integration before

@markmhendrickson markmhendrickson added this to the Stacks 2.0 Mainnet milestone Jan 7, 2021
@friedger
friedger changed the base branch from master to release/connect-2 January 7, 2021 13:54
@friedger
friedger force-pushed the chore/remove_blockstack branch from c36dd9c to e5975fd Compare January 7, 2021 14:47
@hstove

hstove commented Jan 8, 2021

Copy link
Copy Markdown
Contributor

Hm, some funky stuff happening with actions. The "Publish npm betas" and "publish firefox beta" aren't supposed to run - the jobs have if: github.repository == 'blockstack/ux'.

@hstove hstove left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There do seem to be a bunch of legit Typescript errors. I would make sure that yarn typecheck works from a clean build (you might need to rebuild node_modules if you can't repro locally).

@hstove
hstove force-pushed the release/connect-2 branch 3 times, most recently from d0d2a9f to 6957c04 Compare January 9, 2021 20:36
@hstove

hstove commented Jan 12, 2021

Copy link
Copy Markdown
Contributor

This is now in #758 , so closing!

@hstove hstove closed this Jan 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants