Warning: Version mismatch detected between ArcGIS API for JavaScript and assets

926
2
Jump to solution
05-05-2021 10:02 AM
JamesGough
New Contributor III

I recently migrated a project from consuming the ArcGIS Javascript API through ESRI-Loader to ES Modules.

Today I noticed this warning appearing in the browser console:

 

[esri.core.workers] Version mismatch detected between ArcGIS API for JavaScript and assets:
API version: 4.19 [Date: 20210423, Revision: 33983ad1]
Assets version: 4.19 [Date: 20210504, Revision: dd3facdb]

 

 

I have version 4.19.1 of the "@arcgis/core" package installed and importing the assets with this line in my index.css:

 

@import "https://js.arcgis.com/4.19/@arcgis/core/assets/esri/themes/light/main.css";

 

 

 I'm guessing this warning is just because of a new minor release, It looks like 4.19.2 is out now.

But that raises two questions.

  1. Is this something that I need to worry about? Can different minor releases between the JS and assets cause issues?
  2. Is there a way to pin the minor version being imported from the CDN for the assets? Or for a production build should I switch locally installed assets?
1 Solution

Accepted Solutions
ReneRubalcava
Frequent Contributor II

You could point the assets to the specific version you want to match using jsdelivr

https://www.jsdelivr.com/

 

Typically, these warnings don't have much impact at the patch level. For production, if you want to be completely bullet-proof, you can use jsdelivr or copy the assets.

And we don't typically patch the CDN post-release, just something came up. NPM would only get patched if I messed something up, which has happened before... my bad.

View solution in original post

0 Kudos
2 Replies
ReneRubalcava
Frequent Contributor II

You could point the assets to the specific version you want to match using jsdelivr

https://www.jsdelivr.com/

 

Typically, these warnings don't have much impact at the patch level. For production, if you want to be completely bullet-proof, you can use jsdelivr or copy the assets.

And we don't typically patch the CDN post-release, just something came up. NPM would only get patched if I messed something up, which has happened before... my bad.

0 Kudos
JamesGough
New Contributor III

Thanks for the response, and the link to jsdelivr, have not heard of that before but it looks cool.

Glad there shouldn't be any issues for now. When i'm ready to deploy for production i may use one of those options.

0 Kudos