How to use locally modified @atproto/api with social-app? #2669
-
|
I have made updates to @atproto/api (rich-text) in my fork, and I have used "yarn link" to link the @atproto/api package reference in social-app to point to my local package/copy. I am running the atproto dev server. My IDE picks up the updated api signature's, but running social-app indicates to me that it is not picking up the modified api at all. Is there another approach I should be using other than "yarn link"? When running social-app, it doesn't seem to be using the local dev server as well... |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Very reasonable question! I don't work with the JS ecosystem as much, and don't have a reliable answer for you. We do have some docs for linking when doing Ozone development against a patched version of the api package: https://github.com/bluesky-social/ozone/blob/main/HACKING.md We are planning to change how the api package works to make it more app-agnostic, and improve docs on building and working with independently-designed Lexicon schemas in the near future. Maybe that will help! |
Beta Was this translation helpful? Give feedback.
-
|
I'm marking this as the answer because it seems to be correct. I'm realizing now that the social-app doesn't seem to actually hook up to the dev-env just because I am running it, it's always pulling from the live public urls, and I have yet to figure out how to make it use the local app view server from the dev-env. |
Beta Was this translation helpful? Give feedback.
-
|
@bnewbold what should be done when lexicon modified? social-app has golang code in social-app/bskyweb/cmd/bsyweb/server.go in case of ozone, ozone doesn't have golang code so HACKING.md works. |
Beta Was this translation helpful? Give feedback.
Very reasonable question! I don't work with the JS ecosystem as much, and don't have a reliable answer for you. We do have some docs for linking when doing Ozone development against a patched version of the api package:
https://github.com/bluesky-social/ozone/blob/main/HACKING.md
We are planning to change how the api package works to make it more app-agnostic, and improve docs on building and working with independently-designed Lexicon schemas in the near future. Maybe that will help!