Skip to content

outputPath is not respected, a timestamp is always added #2

@n2o1988

Description

@n2o1988

Hi there 👋
I've discovered this project and I'm using it with some good success, but I found an issue that should be easy to fix: the provided outputPath is not fully honored as the resulting file always has an extra timestamp attached to it.

Example

await recorder.startRecording('/tmp/video.mp4', {...});
...
const result = await recorder.stopRecording();
console.log(result.outputPath); // shows "/tmp/video-1767787936862.mp4"

This forces the consumer to having to rename the file, which is a bid weird given the correct and final path was given as an input.

Could this (I presume temporary?) timestamp be removed automatically by the library?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions