Latest Contributions by AndyGup

It's hard to tell without a repro example. These errors can often show up when using local assets that haven't been configured. Take a look at this doc and see if any of the info helps: https://developers.arcgis.com/javascript/latest/working-with-assets/#copy-and-point-to-local-assets, for example be sure to configure the assets path. For more info on minimal repro apps: https://developers.arcgis.com/javascript/latest/troubleshooting/#minimal-reproducible-application.  ... View more

@LefterisKoumis good catch on the documentation bug in the tutorial. We'll get it changed from unit(s) to unit, which is the correct parameter. It's documented in both the geodeticAreaOperator and geodeticLengthOperator under options.. ... View more

Hi @AFackler_NAPSG since you are getting a native firmware error message directly from the AMD driver, this is most likely a hardware problem, and not an issue with the ArcGIS JavaScript SDK which powers Experience Builder, Dashboards, Map Viewer, etc. You mentioned thinking the same thing in your comment here. Based on your descriptions in this particular case, the browser's WebGL2 support error message is being caused by the underlying laptop hardware failure. ... View more

@JoelBennett the 4.33 downloads have been updated. ... View more

@NiklasKöhn  thanks for the feedback. Correct, there's currently no replacement for pointFromDistance(). We are looking into options for that. ... View more

@DavidWilton  interesting, I'm not sure why those two modules are being loaded. I'll refer this issue to the web components devs and we'll take a look. Thanks for reporting. ... View more

We've experimented with comlink and Vite/rollup. We'll have a sample app for that when 4.33 releases in the next 30 days or so. You might give it a try with Angular and let us know: https://github.com/GoogleChromeLabs/comlink. ... View more

@MichaelWen_Timmons  typically 404 errors indicate something is not configured correctly. Verify the assets were actually copied: https://developers.arcgis.com/javascript/latest/get-started-npm/#local-assets. Please provide a minimal reproduction sample. Here's our troubleshooting guide for future reference. ... View more

Please provide a minimal repro sample, there's more info on that here: https://developers.arcgis.com/javascript/latest/troubleshooting/#minimal-reproducible-application. One suggestion is to first build the custom layer in JavaScript, and then migrate your code to TypeScript.  Did you try adding a load() method. There are several samples to use for guidance: https://developers.arcgis.com/javascript/latest/sample-code/layers-custom-tilelayer/ , https://developers.arcgis.com/javascript/latest/sample-code/layers-custom-blendlayer/ and https://developers.arcgis.com/javascript/latest/sample-code/layers-custom-elevation-exaggerated/. > I don't suppose a dojo-less typescript version is on the cards, is it?  There hasn't been any dojo in the 4.x API in quite a while, and it was removed from the CDN in version 4.25. ... View more

@bearingwestlooks like I never clarified my answer from above. If you are using TypeScript with '@arcgis/core', then the error "Property 'createSubclass' does not exist on type 'typeof SomeXYZLayer'" is correct when attempting to use the createSubclass() method. The createSubclass() method only works in JavaScript. We updated the documentation about subclassing in TypeScript here: https://developers.arcgis.com/javascript/latest/implementing-accessor/#create-a-simple-subclass.   The correct pattern in TypeScript would look like the following. You might also need to set 'useDefineForClassFields:false' in your tsconfig, depending on your project configuration. import { subclass } from "@arcgis/core/core/accessorSupport/decorators"; import BaseTileLayer from "@arcgis/core/layers/BaseTileLayer.js"; @subclass("custom.MyTileLayer") export class MyTileLayer extends BaseTileLayer { // TODO }   ... View more

@FC_Basson, thanks for the heads-up. I'll open an issue to get that added at 4.33. I'm not sure why the property didn't get exposed in the component. ... View more

Good catch on the wording, I'll blend your suggestions in. We agree that some of the wording could use "fine tuning". The first phase was to get all 60+ new operators into the API, now we are in the enhancement phase. ... View more