arcgis-js-api | Minified version of the ArcGIS API for JavaScript | REST library

Ok, so it seems that the parameter of CustomContent creator function is of the form {graphic: Graphic}.

The never error is because not type was assigned, so you can assign any to actually avoid it. I am not exactly sure of the correct type.

This is the key part of the example,

If you just want to create the default popup template (the table with all the fields), then you just need to use FeatureLayer function createPopupTemplate, it will do everything for you (ArcGIS JS API - FeatureLayer createPopupTemplate).

Now if you want to do some extra configuration, you can use the same method or popupUtils method, wich has an extra parameter.

Here is an example I made for you to show a possible use, in there all I do is to change alias values to make it look nicer.

Your package.json has a mix of dev dependencies with versions that start with ~ and ones that start with ^. That's probably because some dev dependencies were installed with older versions of npm that defaulted to ~ which is more conservative than ^. As a first step, change the 8 ~ versions to ^, remove node_modules and (if it exists) package-lock.json and run npm install again. I tested this locally and it didn't reduce the number of vulnerabilities reported by npm audit but it did reduce the number of outdated packages which is a step in the right direction.

Let's simplify things by only looking at the audit results for your production dependencies and ignoring (at least for the moment) issues in your dev dependencies. npm audit --only=prod reports only 5 issues, all moderate. Running npm audit --only=prod --force fix updates @capacitor/cli from 2.x to 3.x. That's a breaking change so you'll want to test it, but if that works for you, congratulations because npm audit --only=prod reports no vulnerabilities.

At this point, you could possibly choose not to worry much about the other issues reported by npm audit. However if you wanted to fix them, here is the potentially tedious/arduous path I'd recommend:

• Do a manual audit of all of your dev dependencies to make sure you aren't including things you don't need. Maybe you have things that are installed that you aren't using. Uninstall them. Maybe you have things installed that are nice-to-have but you don't really need. Consider uninstalling them too.
• Run npm outdated to see what could be manually updated via a breaking change. Try doing those updates.

Try upgrading to 4.19. What you are seeing looks like a configuration issue that was changed at 4.19.

I checked the browser console and noticed that the url being sent to the proxy instead of this

http://localhost:3030/proxy/https://maps.disasters.nasa.gov/ags04/rest/services/ca_fires_202008/sentinel2/MapServer?f=json

looks like this

http://localhost:3030/proxy/https:/maps.disasters.nasa.gov/ags04/rest/services/ca_fires_202008/sentinel2/MapServer?f=json

Not sure why it's happening, but as a quick fix you can replace

Ok, I think now we can summarize.

In order for this to work you need to set a proxy. Like you mention ESRI provides some implementations on different techs.

I fork their repository in order to include an easy test setup using docker and docker-compose. resource-proxy fork

After clone it run,

You will not be able to add external data like a field. But you could use a function to define the content. Take a look at this example that I made for you, in there author is the global value.