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
{{ message }}
This repository has been archived by the owner on Feb 25, 2019. It is now read-only.
With npm allowing us to use namespaced package names and our current theme of @trust/jwX packages, it may be desirable for us to split JWD into it's own package that depends on @trust/jwt.
If we do decide to do this then we should probably only do it once JWT is refactored and working as intended.
Thoughts?
The text was updated successfully, but these errors were encountered:
I strongly agree about JWD eventually becoming it's own package. Not sure about the order of extraction or initially grouping JWD here. Thinking it will become apparent as we sort out some of the current design challenges.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With npm allowing us to use namespaced package names and our current theme of @trust/jwX packages, it may be desirable for us to split JWD into it's own package that depends on @trust/jwt.
If we do decide to do this then we should probably only do it once JWT is refactored and working as intended.
Thoughts?
The text was updated successfully, but these errors were encountered: