chrome-extension | Building a simple Chrome extension using React | Browser Plugin library

adding w.Header().Set("Access-Control-Allow-Headers", "Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers") solved the issue.

In order to interact with an ERC20 token, you have to create an instance of it from the desired contract. You would need to import ERC20 to your nfts contracts, and then create an ERC20 token instance pointing to your token. It would be something like this:

MDN Says:

For example, for any MIME type whose main type is text, you can add the optional charset parameter to specify the character set used for the characters in the data. If no charset is specified, the default is ASCII (US-ASCII) unless overridden by the user agent's settings. To specify a UTF-8 text file, the MIME type text/plain;charset=UTF-8 is used.

So, for anything based on text/... you can optionally add the charset.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#structure_of_a_mime_type

The following update to contentType() function demonstrates one solution.

You are using a named function when you add a listener in order to pass it as a parameter, also, you only pass the listener to be removed, which should be the second parameter, after you define the event from which you are removing the listener. However, that's not the right approach. Instead you should define your function separately, like

Okay I've solved the same problem. Seems if you send a request with cookie to the Instagram's API, it will return 403 back. In iOS, URLRequest by default will add some cookies by the system, which causes this 403 problem.

What you need to do is add:

Okay so we figured out with @A7x what the problem was.

React can't access .env files if they are outside of it's working directory even when using dotenv and path.resolve

A seperate .env dedicated to React is needed in it's root directly, variables need to be prefixed with REACT_APP_ and there is no need to call require("dotenv").config()

Make sure to restart your server whenever changing/creating your .env file else changes won't be reflected.

By adding "module":"CommonJS" you are telling TypeScript to generate Node.js-like JavaScript, which is passed properties from its wrapping function arguments on execution such as exports (hence why it added code expecting it).

By default, TypeScript is generating JavaScript to be EcmaScript6-module compliant however the HTML script tag doesn't try to read modular JavaScript by default. One thing you can try, after you remove the module config setting and rebuild, is add the type attribute with the value module explicitly in your HTML:

Add schema to URL:

After searching through the Mozilla Development Network (MDN), I found a solution (linked here) for my extension that works with Safari. It involves detecting tab changes instead of history state changes, shown below.

manifest.json: