Broken imports from maplibre-gl about maptiler-sdk-js

[jonathanlurie]

Hello @moose115 , sorry for the inconvenience. I found an issue yesterday that may b related to the issue you are experiencing: try to modify your tsconfig with moduleResolution to "Bundler" (instead of "Node").

I am investigating why this issue even happens, as the TS config did not change and MapLibre's did not either.
Let me know if that helps.

[moose115]

Thank you for your response @jonathanlurie! Already had the property set to "bundler".

Found the issue, it has to do with new caching (but like I thought, it's just imports that are causing it). In caching.ts one of functions imported form maplibre-gl is addProtocol. I don't know why exactly, but for some reason rollup wants to import that function in particular separately via named imports, and fails miserably because maplibre-gl is a CommonJS module.

Importing maplibre-gl as default import in caching.ts, and then accessing the function with maplibregl.addProtocol prevents the function to be imported separately. (Edit: I think that wouldn't be too neat, could even be a code smell)

That function can be imported from index.ts instead, where it is already imported and re-exported anyway. I'll submit the PR soon (#79).

[jonathanlurie]

Hey @moose115 , thanks again for your fix, it is now part of the v2.0.1 available on npm!

[kyoshino]

I’m also working on a SvelteKit project, and looks like the SDK v2.2.0 has reintroduced the issue 😕

[jonathanlurie]

Hello @kyoshino , last week I pushed v2.2.1 with a fairly different export strategy, could you try it and let me know? If it does not work for you, can you please open another issue with more details specific to your use case?

[wgro]

I am also experiencing this issue with a SvelteKit project and 2.2.0.

[kyoshino]

Tested this again. The issue was reintroduced with v2.2.1, not v2.2.0. I have filed #99.