Closed zachsa closed 2 years ago
This should be working now - turns out the build was crashing, and I was able to track down the memory leak!
Thanks very much!
Was it while building this library? I actually had a realization that the same thing may have been happening in a new version of the maplibre-gl library.
I was going to check this tomorrow
I may have spoken too soon, it seems to still be held up in the package upload pipeline due to the file count.
I see that the new version is accessible via the CDN. Does that mean it's working completely?
Also, ideally import map generation would fail if exact versions can't be matched - or at least there should be a console warning
Looking at this now - the same thing happens for another library:
npm install maplibre-gl@2.2.0-pre.3
The import map then specifies an older version of this library:
"maplibre-gl": "https://ga.jspm.io/npm:maplibre-gl@2.1.9/dist/maplibre-gl.js",
But in this case the newer library version does appear to be available via the JSPM CDN - https://ga.jspm.io/npm:maplibre-gl@2.2.0-pre.3/dist/maplibre-gl.js
This build should be working now, and with the override as well.
Bug
JSPM Generator is producing an import map with the
@arcgis/core
library version specified incorrectly.In
package.json
(andpackage-lock.json
) the version is specified at4.24.7
. But generating the import map results in importing the library at a lower version than specified (4.23.7
). So far I have only noticed this with the@arcgis
libraries (and not, for example, the@mui
libraries).On a possibly related note. Trying the
ga.jspm.io
link for the4.24.7
version gives me a404
error:To Reproduce
In a new directory:
Create the following files
index.html
index.js
jspm.js
Generate the import map
The output.html file shows the incorrectly resolved package version