iconv-lite | Convert character encodings in pure javascript | Base64 library

I looked at the docs and you need to pass a React Component as the first argument of the styled function. In your example you are passing a function component without defining the type of the "props". But the type of "props" default to {} as you can see here. That's why you are getting the error.

So you simply need to provide the type of your props like so:

Counterintuitively, each stream middleware needs its own "error" listener to handle stream errors correctly.

The stream variable is missing the error listener in OP's snippet. Consequently, an unhandled (asynchronous) error is raised when reading a non-existing file.

Its not a breaking error, just means that some functionalities might not work as expected. As this npm WARN EBADENGINE required: { node: '>=0.8 <=9' } line shows, the required node version for this package to work as intended is between 0.8 and 9 but you have node 16.

After a lot of investigation, we found that it was a dependency called gettext-parser that was issue. gettext-parser was not meant for browsers. Webpack polyfilled the required node.js modules and one of them was body-parser and then in turn iconv-lite.

We found this by updating to Angular 12 when webpack@5 stopped polyfilling node.js dependencies and it started to throw errors during the build.

I hope we don't need encode or decode response data, we can simply use "parse" for buffur data to response json.

JSON.parse(responseData);

Use axios with the config option responseEncoding set to 'binary' like so:

Turns out I need to set the environment variable LC_CTYPE for pbcopy:

In case someone who got the same problems, here my solution.

I have solved this by using a Linux server.

It's important to understand what a character encoding is and isn't.

A text file is actually just a stream of bits; or, since we've mostly agreed that there are 8 bits in a byte, a stream of bytes. A character encoding is a lookup table (and sometimes a more complicated algorithm) for deciding what characters to show to a human for that stream of bytes.

For instance, the character "€" encoded in Windows-1252 is the string of bits 10000000. That same string of bits will mean other things in other encodings - most encodings assign some meaning to all 256 possible bytes.

If a piece of software knows that the file is supposed to be read as Windows-1252, it can look up a mapping for that encoding and show you a "€". This is how browsers are displaying the right thing: you've told them in the Content-Type header to use the Windows-1252 lookup table.

Once you save the file to disk, that "Windows-1252" label form the Content-Type header isn't stored anywhere. So any program looking at that file can see that it contains the string of bits 10000000 but it doesn't know what mapping table to look that up in. Nothing you do in the HTTP headers is going to change that - none of those are going to affect how it's saved on disk.

In this particular case the "file" command could look at the "encoding" marker inside the XML document, and find the "windows-1252" there. My guess is that it simply doesn't have that functionality. So instead it uses its general logic for guessing an encoding: it's probably something ASCII-compatible, because it starts with the bytes that spell in ASCII; but it's not ASCII itself, because it has bytes outside the range 00000000 to 01111111; anything beyond that is hard to guess, so output "unknown-8bit".