Map Not Loading – CDN Error – Urgent Assistance Needed

Mappedin JS
1

We are currently experiencing an issue where the map is not loading on our application due to a CDN-related error. This issue is affecting our users and needs to be resolved as soon as possible.

We kindly request your immediate attention to this matter. Please see the attached screenshot for reference.

image
image547×477 16.9 KB

Thank you in advance for your quick support.

2

What is the full URL you are seeing the 404 on? I tested the following, which are working. Are you still seeing this issue?

https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js@beta/lib/index.css

https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js@beta/lib/esm/index.js

1 Like
3

Now issue has been resolved
We are using the following CDN links:

https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js/lib/index.css

https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js/lib/esm/index.js

4

Thank you for your response.

To clarify, in our current implementation, we are using the following CDN URLs:

  • https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js/lib/index.css
  • https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js/lib/esm/index.js

However, we are encountering intermittent 404 errors with these links, which is affecting map loading in our production environment.

You mentioned using the following URLs with the @beta tag:

  • https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js@beta/lib/index.css
  • https://cdn.jsdelivr.net/npm/@mappedin/mappedin-js@beta/lib/esm/index.js

Could you please confirm:

  1. Whether the @beta version is stable for production use?
  2. If not, what version (e.g., a specific version tag like @1.76.0) would you recommend using in the CDN path to ensure stability and avoid downtime?
  3. Is there a versioning strategy or recommended practice to prevent such outages in production environments?

We’d like to make sure we’re using the most reliable and supported CDN path to avoid any further disruption for our users.

Looking forward to your guidance.

5

Mappedin JS version 6.x is currently in beta. It’s Release Notes page lists all available versions. We expect it to move out of beta this month. Current v6 beta releases are stable for production use.

Those 404 errors are from jsDelivr, which is a public distribution network where Mappedin publishes its library. They may have been having an outage causing these errors.

To avoid this, you could build the Mappedin JS library into your app, which will result in it being hosted from your own web server and not rely on jsDelivr. Both approaches are documented in our Mappedin Getting Started Guide. Your app is using the “Local Development without NPM”, which results in reliance on jsDelivr. If you wish to keep that approach instead of building Mappedin JS you could try the alternative distribution network unpkg if jsDelivr is proving to be unreliable.