runkit | Runkit | REST library

I have finally figured this out after a professor sent resources to explain the error. Basically, you need to download to nodev12.20.2 in order to use p5 serial (probably because of outdated dependencies)

I did this by running the following in the terminal. You can use nvm to run different versions of node, so I suggest using it to install node if you didn't already:

if the RegEx engine supports Unicode then you can try to match the unicode instead of characters. see here

BigInteger is storing numbers in a way that allows them to track numbers bigger than what JavaScript can track. How they do that you should consider a black box - when you are ready to go back to a normal int, you need to do bi.negate().intValue(), or if it really is too big, bi.negate().toString()

https://runkit.com/davidjwilkins/example-bigint

The root cause of the problem is the downloaded image didn't follow the base64 requirement. There is nothing wrong with the JSZip part.

Here are different ways to download the image properly:

Node

I managed to replace the image downloading library from request to node-base64-image and everything is working now. I guess you can still use request but need to tune the parameters in order to get that work. Here is the working Runkit. So in conclusion the problem is on download side.

Browser

As I want to download the image from the using a browser script (tampermonkey) so the node solution doesn't fit me. After searching a bit I find a working solution:

First using stack exchange's user api here, you are able to attain your stack overflow account information in JSON format via an endpoint url. All you have to do is to specify your stack overflow user id in the id field and click run to generate the endpoint path. You can attain your stack overflow user id by clicking on your profile picture, it will then appear in the search bar.

Append the path generated to https://api.stackexchange.com to form the endpoint url.

My stack exchange endpoint url: https://api.stackexchange.com/2.2/users/9133459?order=desc&sort=reputation&site=stackoverflow

Now that we have our stack overflow information in JSON format, we can proceed to parse it and create a new endpoint which meets shields requirements. To do that you would have to create an account with RunKit. Publish this piece of code on RunKit and make sure the node version is v4.9.1 (replace the url in the code with your own endpoint url generated previously):

Runkit defines a lot of environmental variables that are sufficient to detect this. More specifically, we can detect RUNKIT_ENDPOINT_PATH, RUNKIT_ENDPOINT_URL, RUNKIT_MOUNT_PATH and RUNKIT_HOST:

All right, so here is the problem, the Access-Control-Expose-Headers must also be presented in the headers of response to non prefight reqeust. After I exposed this headers to all response, I can get access to the Authorization header in my vuejs app.

Can't reproduce it. It works for me.

logger.js:

Based on your example code, the problem is your preparation of the string array which has broken up the string-with-spaces before the parser gets to see it: