Nuxt Application - Architecture

Adopt Nuxt Folder Structure

[ ] Create Feature Branch *Keep in sync with main
[ ] Identify core components and organize them under components/.
[ ] Move individual view files under pages/, ensuring they maintain routing integrity.
[ ] Transfer global state management files into Nuxt’s store structure if using Pinia.
[ ] Considerations: Since routing in Nuxt is file-based, carefully map the routes to Nuxt’s structure to avoid broken paths.
[ ] Remove Boilerplate Code and Module Import/Exports
[ ] Gradually remove any import/export statements for components, plugins, and pages that Nuxt can auto-import.
[ ] Refactor module code to use Nuxt’s global access patterns to reduce redundancies.
[ ] Considerations: Keep track of all manually imported modules to avoid accidental removal of necessary dependencies.
[ ] Maintain Single Page Application and Current State Management
[ ] Configure Nuxt as an SPA to avoid SSR complexities during the initial migration.
[ ] Refactor only where necessary for compatibility, keeping the state management unchanged.

bcgov / entity