We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parseFile
10.3.1
Using Bun as runtime, the console remains idle when parseFile is called.
Here is the following code. This code works well with npm and tsx.
npm
tsx
Also, on line 1, I get the following error from typescript: Module '"music-metadata"' has no exported member 'parseFile'
Module '"music-metadata"' has no exported member 'parseFile'
import { parseFile } from 'music-metadata' import { inspect } from 'util' const filePath = '/path/to/file.mp3' async function main() { try { const metadata = await parseFile(filePath) console.log(inspect(metadata, { showHidden: false, depth: null })) } catch (error) { console.error('Error parsing metadata:', error.message) } } await main()
Should read properly the metadata of the given file
The text was updated successfully, but these errors were encountered:
Bun explicitly has a policy if it works in Node but not in Bun, it is a Bun bug, you should report it there.
Sorry, something went wrong.
This works:
Bun.file(filePath) .arrayBuffer() .then((buffer) => new Uint8Array(buffer)) .then((buffer) => parseBuffer(buffer, { path: filePath }, { duration: true }) )
No branches or pull requests
Is there an existing issue for this?
music-metadata version
10.3.1
Current Behavior
Using Bun as runtime, the console remains idle when
parseFile
is called.Here is the following code. This code works well with
npm
andtsx
.Also, on line 1, I get the following error from typescript:
Module '"music-metadata"' has no exported member 'parseFile'
Expected Behavior
Should read properly the metadata of the given file
Attached audio sample?
The text was updated successfully, but these errors were encountered: