Latest Contributions by StevenGreenwaters

I finally solved this issue. I was getting exactly this same, "No hook for resolver normal in object ResolverFactory" error on two completely different computers every time I would run "npm start". Over six months, I tried many more times hoping a newer version of Esri's CLI would resolve this issue. I also tried the solution above about downgrading Webpack, and a solution on the Dojo Webpack Plugin repo about deleting node_modules/* and package-lock.json and re-running "npm install", but still kept getting the same error. Eventually after spending a significant amount of time on this, I discovered the original problem occurred during the "arcgis create project" process. Even though it clearly shows in bright green and bold text "Done! Your ArcGIS JSAPI application has been installed!", if you look closely above that in light gray text it also says, "Oops, something went wrong." I didn't pay much attention to that the first 20 times because it's completely normal to see warnings and errors when installing a Node project. But this one turns out to be a critical failure from which there is no return. The solution turned out to be amazingly simple. Although installing the Windows Build Tools required running PowerShell as an administrator, I had to then switch to either a regular Command Prompt or Node.js Command Prompt (as a non-administrator) to execute "npm install -g @arcgis/cli" and "arcgis create arcgiscli". Now the Esri CLI installs and "npm start" works perfectly every time.  I hope by sharing this solution I can spare someone else months of delay and countless hours of wasted time. ... View more

Esri made WebGL the default instead of SVG when the JavaScript API version 4.9 was released in September 2018. The following blog post says, "Starting now, WebGL rendering is out of beta and is the default rendering engine... For now, if you have a requirement to use SVG instead of WebGL for rendering, you will be able to configure your app to use SVG. However, starting with 4.10 (December 2018), WebGL is the only planned rendering mechanism." https://www.esri.com/arcgis-blog/products/js-api-arcgis/announcements/jsapi-4-9/ Sure enough, when the JavaScript API version 4.10 was released in December 2018, the release notes said, "WebGL is now used for drawing all layers in a MapView." https://developers.arcgis.com/javascript/latest/guide/release-notes/index.html That means WebGL support in users' browsers is now mandatory even for 2D maps-- not just 3D maps. I am shocked Esri would go from having SVG be the default rendering mechanism to completely dropping all support for it wholesale in a span of only three months. Support for SVG should have been retained for years after whenever WebGL was no longer the default. Since there are still tons of brand new computers out there that have limited or no support for WebGL, if you want your web applications to function at all, you are now stuck like a brick wall with the JavaScript API version 4.9. Our federal agency will not be able to benefit from any of the improvements in version 4.10 and above for many years because of this decision. On my maxed out, highest-end Dell Latitude, I now see a blank hole instead of a map for every single one of the sample applications. What on earth? ... View more