-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing devtool option from webpack config is causing webgl errors in production #67
Comments
Try updating to 4.17 or even better is switch over to using our ES modules build => https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli. Reference: https://developers.arcgis.com/javascript/latest/guide/es-modules/ |
Oh wait, sorry! I was able to reproduce this with our ESM build running @arcgis/core 4.19.0-next.20210119. This is a larger issue within the JS API. I'll open a bug report. |
Andy, Also, I had to change the following lines in my code: --Thanks |
Yep, thanks. We think there's a problem when using the JS API with Angular + webpack + terser when creating production builds. There's a compression variable setting in the terser library that's causing some functions to flatten during the uglify step and then the optimizer sets them to |
@gamreddy to fix the WebGL errors try setting |
Andy, build size has more than tripled with that setting. |
An increase in on-disk size is expected. Did it affect the size of the initial API load in the app? |
Andy, size change in the initial API load seems negligible. |
Hi,
Removing devtool:'eval' from extra-webpack.config.js (webpack configuration) for production release is causing webgl errors when using featureReduction property on FeatureLayer.
Errors in browser console:
WebGL: INVALID_ENUM: texImage2D: invalid type
WebGL: INVALID_ENUM: texSubImage2D: invalid type
Following is my initializeMap() method in esri-map.component.ts:
async initializeMap() {
}
Thanks
The text was updated successfully, but these errors were encountered: