Project:Map

Map

• 2/27 - Setting up Nuxt environment.

• Expected as:

• SSG <- rather, ssr:false
• SPA
• Leaflet (Module)

• Initial thoughts are the tooling is great but CLI interactions are the real highlight.
• Nuxt's on-install DX offers quite a lot of flexibility without creating a monolith upon initial setup.
• Unlikely to need anything from SSR and its qualities. Leaflet is best handled client-side.

• However, the plan for modlist tokens means there will need to be authentication (silent) to communicate with user created configurations.
• Nitro's exact role is projected to be limited or on-use, if used. Need to dig here -> see the protected API calls and background mini-sync.

• 2/28 - Vue? Nuxt?

• What is actually true is "ssr:false", at least as far as Leaflet is concerned.

• Since it operates (exclusively) in the client realm the biggest questions are:

• Prerendered with simplified routes? vs --
• Selective prerendering.
• Landing animation? Haven't done hydration tests.
• Auth token from MW? Nitro, hello?

• Leaflet just wants to work. No issues (yet).
• Haven't gotten around to caching strategies, mostly focused on click interactions and the map frame at the moment.

Late night: Spent some time monitoring Nitro operation. Insightful!

It is very clear Nuxt is in active development and sometimes uses experimental features (going as far as recommending them).

This...is not ideal. Even so, the framework is fun and I'm still rather busy exploring JS itself.

Less about "mastering Nuxt" and taming the tiger. I just needed a comfortable JS-like environment to see what the ceiling looked like. It's alright.