New release breaks my code about node-flac-bindings HOT 8 CLOSED

Next I tried to dynamically import so I did:
var flacBindings = require('flac-bindings');
instead of
var flacBindings = require('flac-bindings');

But then I get an error in the next line if I like to create an instance of StreamEncoder:

/home/pi/rooExtend/modPlay.js:928
                var encoder = new StreamEncoder({
                              ^

TypeError: StreamEncoder is not a constructor

from node-flac-bindings.

OK, for all with the same issue I will publish the solution 👍

This was the code before:

var flacBindings = require('flac-bindings');
StreamEncoder = flacBindings.StreamEncoder;
// ... your code continues here...

This is the code that you have to use now. It dynamically loads the module and this takes some time.
Therefore you have to wait and continue asynchronously...

		import('flac-bindings')
			.then(flacBindings => {
				StreamEncoder = flacBindings.StreamEncoder;
				// ... after loading the flac-bindings your code continues here...
			})
			.catch(err => {
				console.log('Cannot load flac-bindings ' + err);
			})

Hope this is useful for someone else but me.

@melchor629
will be great if you might add this to your README file

Best DrCWO

from node-flac-bindings.

Hi DrCWO! Thanks for opening the issue.

This is a known "pain point" of the 3.x series. In release notes I pointed it out that this was happening and added this link https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c which explains a bit what happens and what you can do to fix it. You can always keep using 2.x series meanwhile or use the dynamic import() syntax.

In addition, because I imagined that this would be a recurrent issue, the README also contains this line to warn the devs. I see I should make it even clearer.

Sorry for this confusion. I wanted to move forward with the technology and I know that this can be a bit frustrating. I hope you could find the above link useful.

from node-flac-bindings.