Migrating from Micrio 5.x to 6.x Client 6.x
This page is about the Micrio client version 6. Use the links below to navigate to alternative versions.
If you are already using Micrio 5.x and want to upgrade to Micrio 6.x, there are no migration steps required for v6.0. The data model has not changed between v5 and v6, so your existing custom JavaScript and CSS implementations will continue to work as-is.
Viewport format enforced since v6.1
Since Micrio 6.1, the JS Client API enforces the new [x0, y0, width, height] viewport model. If your custom code uses the JS Client API (e.g. Camera.setView(), Camera.flyToView(), Camera.getView()) with values in the legacy [x0, y0, x1, y1] format, you must update it to use the new [x0, y0, width, height] format.
Example — old format (no longer valid with v6.1+):
micrio.camera.flyToView([.2, .2, .5, .5]); // Legacy: [x0, y0, x1, y1] — bottom-right at (.5,.5)Example — new format (required since v6.1):
micrio.camera.flyToView([.2, .2, .3, .3]); // New: [x0, y0, width, height] — same bottom-right at (.2+.3=.5,.2+.3=.5)See the v5.4 migration guide for more background on the viewport model change.
If you are upgrading from Micrio 4.x or older, please refer to the Micrio 5 migration guide first.
Should I upgrade?
Each Micrio JavaScript major version has a stable working release:
- Version 1.x (2015-2019): Micrio 1.9
- Version 2.x (2019-2020): Micrio 2.9
- Version 3.x (2020-2021): Micrio 3.3
- Version 4.x (2022): Micrio 4.1
- Version 5.x (2024): Micrio 5.5.6
- Version 6.x (2026): micrio-6.1.13.min.js
This means that Micrio projects using those versions will always keep working as they are. If you have a current running Micrio implementation and it works well, there is no need to upgrade.
We also offer limited support on the previous major release. If you find any bugs, please contact us.
What's changed in v6?
Micrio 6.0 is a leaner version of the client:
- WebAssembly has been removed — the client now runs purely on JavaScript and WebGL, eliminating any Content Security Policy (CSP) or compatibility concerns related to WASM.
data-routerhas been removed — the internal URL routing feature (hash-based and static) has been deprecated.- The
updateevent has been deprecated — use specific events (e.g.zoom,pan,marker-opened) instead. - The rendering engine has been optimized for modern browsers using standard web APIs.
Since the data model is unchanged from v5, all your existing markers, tours, embeds, and other content will work without any modifications.
How to update?
Via npm (recommended for project builds)
If you are using a JavaScript/TypeScript project with a build system, the recommended approach is to use the @micrio/client npm package:
npm install @micrio/client@latestThen import it in your project for full TypeScript support:
import type { HTMLMicrioElement } from '@micrio/client';
const micrio = document.querySelector('micr-io') as HTMLMicrioElement;
micrio.camera.flyToView([.2,.2,.3,.3]);This gives you full type checking, autocompletion, and ensures you always have the latest version.
If you are already using @micrio/client from npm, simply run npm update @micrio/client to get the latest v6 release.
Via CDN (direct HTML <script> include)
If you are including Micrio via a <script> tag, replace your Micrio JS reference with the latest version from r2.micr.io:
https://r2.micr.io/micrio-6.1.13.min.js
If your project uses TypeScript declarations:
https://r2.micr.io/micrio-6.1.13.min.d.ts
That's it — replace the old script reference, and everything will continue working as before.