Lexicon cleanup

[aendra-rininsland]

• Removes src/lexicons
• Replaces with imports from respective upstream packages
• Replaces ts-node with tsx, namely because @atproto/bsky doesn't export lexicons
  • See: Export lexicons from @atproto/bsky package atproto#2353
  • Merging Exports lexicon from @atproto/bsky. Fixes #2353. atproto#2354 will allow reverting to ts-node

Fixes #41.

[ungoldman]

Trying to merge this into a custom feed today, and it took me a long while to figure out why it's working successfully with tsx but failing when trying to build and run the program in a production setting from dist.

Need to import from @atproto/bsky/dist/lexicon instead of @atproto/bsky/src/lexicon!

[dholms]

Sorry for the late reply on this & thanks to @haileyok for putting it on my radar.

I agree that the lexicons are pretty noisy in here. And we really weren't sparing in what we copied over when we set this up 😅

However @atproto/bsky is a pretty heavy duty dependency to install (our entire appview service) just to get access to some types. I think the proper way to do this will be to have published packages for only the code-genned types which can then be installed by all services that use them (including the appview & the feed generator).

An alternate approach would be to add the actual relevant lexicon (JSON) files to the project and also add a codegen command to the package.json. That's the approach that we use on several of our other services.