.upload() is not a function?

[AliAryanTech]

Describe the bug
Well, I'm trying to test .upload but the terminal saying it's not a function? even I tried all examples of .upload it's saying it's not a function.
also storage.once(), saying the same it's not a function.

To Reproduce

const { Storage } = require('megajs')

const storage = new Storage({
  email: '****', // email address 
  password: '*****' // my password 
}, error => {
  return console.log(`${error ?  "Some error happened" : "User is now logged in"}`)
}).ready 

storage.upload('hello-world.txt', 'Hello world!', (error, file) => {
  if (error) return console.error('There was an error:', error)
  console.log('The file was uploaded!', file)
})

Expected behavior
I tried in termux & replit it test the code!
Termux

Replit:

Additional context
One more thing can you tell me an example with a Buffer? Like how to upload a Buffer, I saw those example but coz of upload function unable to test upload by buffer, that's why I thought it would be better if you tell me an example!!

let buffer = await getBuffer("https://telegra.ph/file/e991bb4b535a0f1425aa0.jpg")

const file = await storage.upload('hello-world.txt', Buffer.from(buffer, 'base64')).complete
console.log('The file was uploaded!', file)

Like this? That's just a buffer, I don't know what's the file name and size!?
Then why this, allowUploadBuffering: true

[qgustavor]

I'm quite confused on what you're trying to do, I don't know your JavaScript background, but seems you are mistaking how asynchronous JavaScript works.

Do you know how to use Promises? And how about callbacks? If not check some tutorial for those topics first.

storage.ready is a Promise, so seems you're missing an await keyword, but at the same time you defined a callback at the same time, which… is weird. Use one or another. Callbacks is the old pattern, promises is the new one, this library support both because backyards compatibility but I recommend learning and using promises as they avoid some issues that callbacks have (like nesting hell).

Seems you are using Node CJS, it does not support top level await, check examples in mega.js.org to workaround this limitation (use a async IIFE). If possible learn and use ESM, it does not have this limitation.

Try learning about async patterns in JavaScript, them fix the login first, that's a lot for now, I will answer the upload question later.

I'm on the mobile client, when I get home I will move this into a discussion because that's not an issue with the library, it's mostly a JavaScript related question. Edit: issue migrated to a discussion.

[AliAryanTech]

Indeed, I'm using Nodejs
But my login working fine with that code. 🤔 now I see I was consoling file, that's why!!

const a = async () => {
const { Storage } = require('megajs')

const storage = await new Storage({
  email: '****',
  password: '****'
}, error => {
  return console.log(`${error ?  "Some error happened" : "User is now logged in"}`)
}).ready 

const file = await storage.upload('hello-world.txt', 'Hello world!').complete
console.log('The file was uploaded!')
}
a()

Here:

I thought it's error, when console file:

console.log('The file was uploaded!', file)

Here:

About Buffer upload:

const buffer = await getBuffer("https://telegra.ph/file/e991bb4b535a0f1425aa0.jpg")

const file = await storage.upload('Buffer.png', Buffer.from(buffer, 'base64')).complete
console.log('The file was uploaded!')

So, it works fine:

Here:

Well, Is there any other way to upload Buffer!?
when I only have buffer don't know size, mimetype, name. Just asking 🤔

[qgustavor]

when I only have buffer don't know size, mimetype, name. Just asking

MEGA requires a file name, you can use any name you want, sometimes I just use "a" just to fill this requirement when I don't care about the file name (which is rare, most people don't want to download something without a name or with a meaningless name).

Mime type is not needed. You need it for HTTP servers, but not for this library, MEGA does not check it at all. If you have a Buffer then its size is just buffer.length, if you pass a buffer to the library it will just get the size from this property and upload the buffer, you don't even need to worry about this.

By the way, your getBuffer function returns a Base64 string? Because you are taking the result from it and converting from Base64 by using Buffer.from(buffer, 'base64'). If the getBuffer function returns a Buffer (which is what its name says) then you can just pass it to upload. If it returns a ArrayBuffer or a Uint8Array (like if this function this calls url => fetch(url).then(resp => resp.arrayBuffer()) you can pass those too to upload if you wish.

[AliAryanTech]

Indeed, getBuffer function return 'arraybuffer'
As you said I can simply pass it:

const file = await storage.upload('Buffer.png', buffer).complete

it's working fine, thank you!

[AliAryanTech]

By the way, how to upload file in new folder storage.mkdir() and whenever we upload any file it only upload to that specific folder, I don't want it create one more new folder of the same name.

Can you give an example?

[qgustavor]

That's out of scope. Use a library specific for that, like the one you cited.

[AliAryanTech]

That's out of scope. Use a library specific for that, like the one you cited.

I was just trying to give an idea, nevermind Ok, and thank you!

[AliAryanTech]

Well, Is this possible, to see file downloading progress in console? Sometimes, it took pretty long while downloading...

and sometimes it get Killed and program exit.

[qgustavor]

https://www.npmjs.com/package/progress-stream https://www.npmjs.com/package/cli-progress

[AliAryanTech]

https://www.npmjs.com/package/progress-stream https://www.npmjs.com/package/cli-progress

I see, btw why the downloading take too much time when the file is nearly +100mb. It should be fast coz, program running on hosting server not localhost?

Well, if you familiar with progress-stream module can you give me example with your megajs