Latest Contributions by AndyGup

Hi @JonathanTiu  Yes, we did figure it out. It's related to fine tuning the API and how it uses workers under-the-hood. The size of the workers is just one parameter out of many that affects the initial load performance metrics. Overall, for our baseline testing apps, those metrics improved between 4.27 and 4.29. With that said, if you have a simple, focused repro app that shows a major performance regression on the initial app load, then please open a Tech Support ticket so they can get this formally documented. ... View more

@JasonDoingMapsto speed up your webpack/TypeScript dev builds, you might look into https://www.npmjs.com/package/esbuild-loader. ... View more

Hi @AndresKasekamp  you'll need to do further testing by removing '@arcgis/core' functionality and calcite elements one-by-one to try and find the root cause. Otherwise there's too much going on in the sample including the calcite react wrapper, calcite-panel, calcite-shell, calcite-shell-panel and various '@arcgis/core' modules. ... View more

Update: the Angular team merged the bug fix. Now we wait for the next release of zone.js. ... View more

Hi @boa_panter please see my comments and post additional information in this other thread: https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/zoom-buttons-don-t-work-in-angular-map-component/m-p/1398115/highlight/true#M84074.  ... View more

Thanks for StackBlitz. See the discussion here for more information on this Angular bug and our suggested (potential) workaround: https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/zoom-buttons-don-t-work-in-angular-map-component/m-p/1398110#M84073 ... View more

Hi @marjbilou can you provide a simple GitHub repo or StackBlitz that reproduces the issue? And, are you are able to upgrade to the latest ArcGIS JS Maps SDK release, which is currently 4.29? Version 4.22 goes into mature support in just a few days, at the end of this month: https://support.esri.com/en-us/products/arcgis-maps-sdk-for-javascript/life-cycle. Here's our Angular sample that might give you some hints on what's not working: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli. The sample is using Angular 17 (latest). Angular 13 is no longer supported by Google: https://angular.io/guide/releases#actively-supported-versions. ... View more

Thanks for letting us know @GabrielWatson. We are aware that the workaround isn't going to work for all implementations. Because of that, we encourage you, @ShaneBuscher1 and anyone else using Angular to thumbs up the Angular pull request. Here's the link: https://github.com/angular/angular/pull/54602. And, we are keeping our eye on it. Footnote: there has been motion on updating zone.js related to the Angular 18-next release. ... View more

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