Upgrade guide
Move custom integrations onto Version 1
Version 1.0 establishes the first stable runtime, Web Component, identifier, registry, and contribution-manifest contracts.
Use the public runtime
Replace dependencies on page-specific globals, injected SVG ordering, underscore-prefixed methods, and undocumented CSS with IndiaMapEngine or <india-svg-map>.
const map = new IndiaMapEngine({
mount: "#map",
src: "assets/maps/india-states.svg",
featureSelector: ".map-region",
featureKey: "slug"
});
map.on("selectionchange", event => console.log(event.detail.id));
map.load();
Keep identifiers stable
Join application data through stable slugs or feature IDs. Census and LGD codes remain separate metadata and must not replace application identifiers.
Validate strict schemas
The boundary registry and contribution manifest schemas are frozen at 1.0.0. Remove unknown object fields, select registry records by ID rather than array position, and run the release validator before publishing.
Publication safety
Only Git-tracked, redistribution-safe assets enter release archives. Review every geographic source and its attribution before redistribution.
Complete checklist
Read the full migration document, the Version 1 stability contract, and the 1.0 release notes.