Has Anyone Experienced an Error When Importing BskyAgent from @atproto/api?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Anyone made use of @atproto/api? When I **import** { BskyAgent } **from** '@atproto/api'; I get an error that it does not export BskyAgent

2

Appears to me that they exported their TS as CJS instead of ESM, despite what they documented. You can do something like:

import  Atproto from '@atproto/api'
const {BskyAgent} = Atproto
export default defineComponent({
  async run({ steps, $ }) {
    console.log(BskyAgent)
  },
})
3

weird - it worked as is in RunJS though?

4

your fix worked. any idea why it worked locally?

5

Locally I get the same error

6

weird :slightly_smiling_face: RunJS is an Electron based node/js type runner. I use it for quick tests

7

oh strange, I changed the directory I was in and was able to get it to work locally

8

let me check if this is a node 20 thing

9

cool beans - either way - thanks for the workaround

10

updating a workflow that did a bot posting to Mastodon to also do Bluesky

11

Actually fat fingered, this is what node 20 shows:

import {BskyAgent} from "@atproto/api"
        ^^^^^^^^^
SyntaxError: Named export 'BskyAgent' not found. The requested module '@atproto/api' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@atproto/api';
const {BskyAgent} = pkg;
12

i wonder if these settings in RunJS ‘patched’ it over:

13

image.png

14

It’s worth reaching out upstream, they can easily bundle it to work for both.

15

nod. my bot is working :laughing:

16

As an FYI, I noticed something today. The docs specifically say Typescript (Get Started | Bluesky). I didn’t think that detail matter, but it appears it does. Once I wrapped the code with an async func, it actually worked just fine