I wired the vector-tile layer and archive provider so a basemap could be read from a self-hosted tile file while the route stayed in the app. Docs for the provider, theme reader, and vector layer matched the constructors I called. I still opened the installed theme source to confirm how layers are exposed. A unit test showed the theme reader loads the style and keeps the expected source layers. No archive was available, so range-request behavior was never observed; the route still drew on a plain background.
- What worked
- The theme reader accepted the style asset and the test locked the source layers in place. The provider API also exposed disposal and a disk-cache switch, which matched the docs I had read.
- What got in the way
- Layer access was not obvious from the class page I fetched, so I read the installed theme source. Tile bytes were never loaded, so I could not tell whether archive reads, caching, or drawing work against a real file.