Latest Contributions by AndyGup

@PavanMungaramy best guess without a repro sample that isolates the issue is this might be related to the click event handling in React or react-navigation/drawer. You could try researching issues in https://github.com/react-navigation/react-navigation. ... View more

> I  believe the issue is due to other libraries I am using in my project @PavanMungara  agreed, without more information this doesn't seem to be an issue with the ArcGIS JS SDK. I wasn't able to repro your popup issue using our minimum React sample here: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-react. I recommend you start with our minimal sample app and experiment with adding/removing 3rd party functionality until you can isolate this issue. ... View more

Hi @PavanMungara, please provide a minimum reproducible application, more details on how to do this are available here: https://developers.arcgis.com/javascript/latest/troubleshooting/#minimal-reproducible-application.  ... View more

Hi @GILBERTNG1  thanks for reporting, this sounds like RDP performance issues that are unrelated to the JavaScript SDK. Does the host machine have a GPU and is this a shared machine?  No GPU can have a significant affect on rendering performance. And, multiple users can cause variations in performance. There are many interrelated factors that can affect RDP session performance such as screen resolution, connectivity speeds (like you mentioned), number and type of users on the machine, GPU, etc. 4K RDP resolution requires a high-bandwidth connection with consistent low-latency. Here's an informative Microsoft article on the topic: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-bandwidth and here are some network guidelines for display resolutions: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/network-guidance#display-resolutions. ... View more

The Angular bug has been fixed in zone.js version 0.14.5. We recommend updating zone.js if you are having issues with the SDK's widgets.  https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli#known-issues ... View more

Hi @RoelGarcia  please provide a repro app: https://developers.arcgis.com/javascript/latest/troubleshooting/#minimal-reproducible-application. This error is likely related to webpack shimming the node crypto library. Without a repro app we can't really offer specific recommendations. You might search for "webpack crypto is not defined" on the internet for ideas. ... View more

Hi @SaurabhUpadhyaya I see you have two recent questions that mention errors related to WebGL contexts. This most likely is related to your ArcGIS code and not an issue with React. Your best option is to provide a vanilla JS codepen using the ESM CDN: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-esm-cdn. That way we can all take a look and provide suggestions. Note, the ESM CDN is for testing and prototyping, only. It doesn't offer the performance of a locally built ESM app. ... View more

I'm not seeing those skips on my local build. Please post a link to a repro sample. ... View more

We haven't seen that error before with Angular/esbuild. Can you provide a repro app so we can examine it in more detail? ... View more

Hi @ForrestLin you'll need to provide a repro app. We recommend using our esm-samples as a starting point: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-angular-cli. Here's our troubleshooting guide for local builds for more info: https://developers.arcgis.com/javascript/latest/troubleshooting/. ... View more

> What is the well-known limitation of ES modules you mention I mentioned it above. Basically, unbundled ES modules (ESM) such as "@arcgis/core" typically perform poorly in a production environment. We are constantly optimizing the ArcGIS JS Maps SDK, however ESM builds require a combination of treeshaking, lazy-load and code splitting (chunking) to create an optimal build output. This isn't specific to ArcGIS, for example you can read about why bundling is recommended in the Vite.js documentation:  https://vitejs.dev/guide/why.html#why-bundle-for-production. > Hence, far and away the biggest improvement I could get in build performance, is an approach that doesn't always re-build the ArcGIS library dependency. Vite.js could really help with your use case of having fast(er) build times. Vite does dependency pre-building to dramatically speed up builds: https://vitejs.dev/guide/dep-pre-bundling. Try this sample app: https://github.com/Esri/jsapi-resources/tree/main/esm-samples/jsapi-vite-ts. On my 5 year old machine it takes 20 seconds for a production build.  For dev builds, it's pretty close to zero on my machine - it takes about 150 - 170ms (milliseconds), and rebuilds are almost instant. And, also to reiterate checking out the new map-components. You can access those via CDN and they include TypeScript types: https://developers.arcgis.com/javascript/latest/components-get-started-cdn/. ... View more

Do you require the Webpack-specific tooling? If not, you might take a look at Vite.js. > The pre-built AMD modules served that scenario, but per above, the TypeScript typings for that are being deprecated. If/when you migrate to (new) map web components, those are typed. > Why is the biggest library I reference (by a huge margin) the only one that doesn't come with a viable pre-compiled option? TL;DR - It stems from a well-known limitation of ES modules. Components will make life much easier in that respect. Currently for ESM there's no ECMA-standard equivalent to the AMD dojo build layers. Those are what makes the AMD ArcGIS CDN much more performant than the ESM ArcGIS CDN. For example, JavaScript module declarations have been in TC39 Stage 2 since 2022, and it could be quite a while before it gets finalized as a standard and then adopted in browsers. ... View more