parseFile() function doesn't exist

[simonsanchezart]

Is there an existing issue for this?

• I have searched the existing issues

music-metadata version

9.0.1

JavaScript module eco system

ECMAScript modules (ESM), music-medata ≥ version 8

Current Behavior

I'm using Tauri + React (ts).
I've installed the module, when I try to import the parseFile() function I get the error:
Module '"music-metadata"' has no exported member 'parseFile'.ts(2305)
There is also no parseFile() defined in core.d.ts

I'm importing it like this:
import { parseFile } from "music-metadata";
"type": "module", in package.json

Expected Behavior

I could import parseFile() by doing import { parseFile } from "music-metadata"; and then use parseFile()

Attached audio sample?

• I have provided sufficient information to reproduce the issue

[Borewit]

As written in the README, parseFile() is exclusively available for Node.js engines. So for sure this not available in React running in your browser.
Which would be pointless as you do not have access to your file system in the browser.

For parsing a File in your browser, you can use the parseBlob().

I have 0 experience with Tauri + React. If Tauri covers the backend, using some kind of Node.js engine, Tauri should be able to give you access to Node.js specific functions. If it does not, you need to raise your issue there.

[joacoespinosa]

Hi @Borewit. I'm facing the exact same problem after updating from 7.14.0 to @latest

Mine is a Node.js app which was working with the mentioned version but breaks with 9.0.1: Module '"music-metadata"' has no exported member 'parseFile'

Thoughts?

[Borewit]

Hi @Borewit. I'm facing the exact same problem after updating from 7.14.0 to @latest

Mine is a Node.js app which was working with the mentioned version but breaks with 9.0.1: Module '"music-metadata"' has no exported member 'parseFile'

Thoughts?

Hello @joacoespinosa, @latest is a moving target, I assume this is v9.0.1

I cannot reproduce your problem, I can only proof parseFile() is accessible in a Node.js engine:

Reference: https://onecompiler.com/nodejs/42jznqj9u

[joacoespinosa]

This is what I observe when using 7.14.0:

And this is what I see as soon as I update the library:

I have just realized that the problem occurs even after updating to 8.2.0. Therefore, the issue I'm facing is not strictly related to v9.0.1

I'll keep digging, thanks.

[Borewit]

music-metadata version 8 & 9 are Pure ESM packages, while version 7 is CommonJS.

To be able to use music-metadata version 8 or 9:

1. Run from an ESM based project (include "type": "module" in package.json)

To be able to import parseFile() :

1. Use Node.js