Latest Contributions by AndyGup

It's related to an Angular bug in zone.js. A fix will hopefully be available in the next zone.js release since the pull request is approved and ready-to-go: https://github.com/angular/angular/pull/54602. We have documented a temporary workaround in our Angular esm-sample's README: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli#known-issues. ... View more

Thanks for providing the repo. We don't see any problems. Since the app contains a framework (Nuxt), it doesn't quite qualify as a vanilla JS implementation, even though its only using hello world map functionality. The framework does create and consume additional files. The application is initially loading1.8 MB (Gzip) of JavaScript which includes both ArcGIS JS SDK and Nuxt/Vue. The on-disk build output of 11 MB includes 2.3 MB of Nuxt. Also, since Vite uses Rollup for production builds, the on-disk build size and main bundle size are some of the most optimized bundler outputs that we track. We compare those stats to our stand-alone Rollup sample app which has a main bundle size of 1.29 MB and on-disk build size of 7.56 MB. That can give insight on the amount of overhead created by a framework. More information on how and why these values can vary is available here: https://github.com/Esri/jsapi-resources/tree/main/esm-samples#bundle-size-and-performance. To recap, the performance metrics we track include: - Initial application load - we make a distinction between JavaScript/CSS/HTML files, and service request data (e.g. tile and query data). - on-disk build output - most of these files are not used on initial load. We do monitor and take into consideration the main bundle size, as well as the size and number of total bundles. ... View more

@D_R_  can you provide a simple codepen, GitHub repo or StackBlitz? The presence of the wasm file is related to something in the app doing client-side spatial reference conversions. I'm guessing the TileLayer is triggering the API to load the projection module. The size of that module is a known issue that we are working on. A hello world map app using a web mercator basemap doesn't load that module, for example: https://developers.arcgis.com/javascript/latest/sample-code/intro-mapview/live/. ... View more

The ArcGIS Maps SDK for JavaScript offers significantly more capabilities. At runtime, your application will only load a portion of the on-disk bundles depending on which @ArcGIS/core modules are used in your project. More info: https://github.com/Esri/jsapi-resources/tree/main/esm-samples#bundle-size-and-performance. ... View more

Hi @FC_Basson just confirming, the app with the graphic layer does work okay on other PCs? For the PC that's not working, can you provide: - PC make and model - Operating system and version - Intel Graphics card driver name and version - browser and version ... View more

Hi @FM1  the Locate widget uses the browser's native Geolocation API. You can listen for the specific geolocation error messages using the widget's "locate-error" event to confirm the information being returned by the browser. Here's the MDN article that describes those errors: https://developer.mozilla.org/en-US/docs/Web/API/GeolocationPositionError. Also, in the Electron documentation: "Geolocation support in Electron requires the use of Google Cloud Platform's geolocation webservice." Have you enabled that webservice? ... View more

Hi @2spatial  have you tried to repro this in a vanilla JS app? That will help sort out the basic JS Maps SDK coding flow and potentially identify if/where React might be tripping things up. And even though you didn't get any errors, here's our Troubleshooting guide for local builds. If you did try vanilla JS, then you'll need to provide a simple Stackblitz, codesandbox or github repo. If you can get this working in its simplest form in a basic React app, then it's easier to migrate the code to more advanced React patterns. Our ESM samples are a great starting point to provide a repro case because they have minimal dependencies. ... View more

Hi @GaryLSheppardJr can you repro in a codepen outside of Angular? On surface this doesn't look like an Angular issue. If not, can you provide a personal github repo or StackBlitz using this sample as your base template=> https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli ? ... View more

Adding on to Sage's comments, this looks like an issue with Express and not related to the ArcGIS JS SDK. Here's a link to their documentation: https://expressjs.com/en/resources/middleware/cors.html. They specify a number of different CORS options that might fix the issue. ... View more

Hi@BryanMc  can you reproduce this outside of Vite in a vanilla JS app using the ArcGIS ESM CDN? Also, we'll need a github repo or stackblitz so we can try to reproduce the issue. Reference: https://github.com/Esri/jsapi-resources/blob/main/TROUBLESHOOTING.md ... View more

This appears to be related to a known issue with Calcite: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli#known-issues. Try disabling the zone.js monkey patching for click events. Here's a diff that shows what you need to do  https://github.com/Esri/jsapi-resources/issues/481#issuecomment-1687048980. ... View more

Thanks for reporting, I am able to repro on 4.28 and 4.29-next. We'll take a closer look. ... View more

Hi @Wittawat  thanks for reporting, I've opened an issue for us to take a closer look. As @Justin_Greco mentions, the Compass widget does take into account spatial references. It's different from the Track and Locate widgets because it has two default icons, one for Web Mercator/WGS 84 (compass needle) and one for all other spatial references (arrow).  ... View more