Description of the bug

Could not find a declaration file for module 'bunnycdn-stream'. 'node_modules/bunnycdn-stream/dist/index.mjs' implicitly has an 'any' type.
There are types at 'node_modules/bunnycdn-stream/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'bunnycdn-stream' library may need to update its package.json or typings.

Steps To Reproduce

Install and import the library into a nuxt3 project.

Additional Information

No response

Description

There is an API method that is not implemented in the library: https://docs.bunny.net/reference/video_getvideoplaydata

Can we please add it? I'm asking because after uploading video with createAndUploadVideo() method, I want to access its urls and length to save to my database.

Additional Information

No response

Hello,

I would suggest changing the URL mentioned below to https://vz-123412341234.b-cdn.net/1234-1234-1234-1234-123412341234/play_720p.mp4 as this is more likely to not be deleted compared to the one found here

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	@types/rimraf

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update vitest monorepo to v2 (major) (@vitest/coverage-v8, vitest)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

First of all congrats on your work!

I have some questions.

1. Is it up to date?
2. Does it create and update all at once?
3. Can I pass more parameters thann just the title and collectionId? I want to pass genres, duration,... It is important to pass those parameters.
4. Is it possible to call the videos based on one parameter passed on the data? Let's say, genre=horror.

Again, thanks a lot! This project is awesome!

Description of the bug

When you try to use the function createDirectUpload the documentation says that collection is optional which is correct but the right key should be collectionId because in the bunny documentation it is the right key used for createVideo function which is the internal function used in the createDirectUpload.

Solution

Steps To Reproduce

1. Call createDirectUpload with the following parameters: title, collection.
2. Your video will upload in the root instead of the correct collection

Additional Information

No response

Hello there, it is me again,

I encountered another bug and wanted to notify you.

When calling listVideos the provided options do not work as you need to pass them as query params and not within the body of the request.

I just had a look at listVideos for now so I'm not sure if this is impactful somewhere else.

The LOC I refer to -> https://github.com/dan-online/bunnycdn-stream/blob/main/src/index.ts#L250

How it should be -> https://docs.bunny.net/reference/video_list

You should take advantage of URLSearchParams something like:

const options = {
    page: '1', <-- string
    itemsPerPage: '10', <-- string
    search: 'hello',
    collection: '1312' <-- should rather be collectionId as you search for id and not the name
}

const urlParams = new URLSearchParams(options)

✌🏼

Description

Think about this scenario:-
I have a public m3u8 video url and i want to upload it to bunny stream. The thing I've to do now:-

• Manually download all the ts files and pack it into mp4 format
• Use upload video api to upload mp4 video to bunny stream

If it is possible to upload m3u8 directly to bunny stream with fetch video api, then it will be super cool!

First things first, thanks so much for building this - super useful tool!

I have quick question - I got a little stuck initially uploading videos, as I was creating a web stream from a File object (obtained through a POST request from a html form) using File.stream(). However, despite the bunnycdn-stream API accepting that and returning a response without any issues, the video on the BunnyStream web interface was showing a 'processing failed' error.

I was able to fix things by converting the web stream into a node.js stream using stream.Readable.fromWeb(readable).

Do you know if this is an issue on the BunnyStream end of things, or that AXIOS is not tolerating a web stream for some reason?

Thanks!

Hari

Description of the bug

I'm using nestjs and I wanted to use createAndUploadVideo to upload the file. Unfortunately, file must be of ReadStream type and createReadStream does not work with buffer and stream properties of my multer file. Any ideas how can I make it work?

P.S. Why there is no getVideoPlayData() method implemented?

Steps To Reproduce

...

Additional Information

No response

Hi,

I was trying to compile my TS code into CommonJS and I encountered this error at runtime:

The same error can be reproduced when creating an empty JS project with the library 'file-type'.
It turned out that the library 'file-type' only supports ESM since version 17. However, version 16 (which supports CommonJS) appears to be still maintained.

I made a pull request to address this issue. The change only involves one function related to setting the thumbnail.
I hope my input was useful and happy to provide more info if needed 👍

Hi,
I faced an issue while using Vitest to run some tests that include this library. My code normally compiles to CommonJS and it works fine, only when I use modules the problem occurs.
However, to reproduce this problem you don't actually need to be using TS, you can simply initialize a new npm project and install bunnycdn-stream library. Then set the type parameter in package.json to "module".

npm init -y
npm install bunnycdn-stream

package.json:

// package.json:
"type": "module"

Then create a very simple index.js:

import { BunnyCdnStream } from 'bunnycdn-stream';
const testBunny = new BunnyCdnStream({ apiKey: 'apiKey', videoLibrary: 'vidLib' });

When you run the file, the following error occurs:

I tried to investigate this problem. I think the problem is due to the version of Axios specified in the NPM library (which is 0.27.2).
If you create a new empty NPM project and install [email protected] and do:

import { AxiosError } from 'axios'

the same exact error will appear. I then tried using [email protected] and it did not show any error.

The package.json file in this GitHub repo specifies version 1.2.6 while the one on NPM specifies 0.27.2

I hope my input was helpful. I'm happy to provide more info if needed.

Hey there,

first off all BIG thanks for this project. I made a video streaming backend and created the requests manually, but switched now to your client as it makes my life much easier.

However, I'm having a problem:

I'm using NextJS (13.1.6) API routes and get the following error:

My code looks like this:

export default withUserGuard(async function handler(req, res) {
    if (req.method !== 'GET') {
        res.setHeader("Allow", ["GET"]);
        return res.status(405).json({ error: `Method ${req.method} Not Allowed` });
    }
    try {
        const mostRecent = await getMostRecentVideos();
        return res.status(200).json({ mostRecent });
    } catch (e) {
        return res.status(500).end();
    }
});

const getMostRecentVideos = async () => {
    const videos = await stream.listVideos({
        page: 1,
        itemsPerPage: 10,
        orderBy: 'date'
    })

    return videos.items.map((video) => ({
        viewTime: prettyPrintSeconds(video.length),
        collection: collectionIdToGenre.get(video.collectionId),
        ...video,
    }));
};

Do you have an idea how to solve that or is there a way to allow CommonJS modules properly?
Thanks and all the best!