/vue-layers

Integrate OpenLayers map in VueJS

Primary LanguageVue

vue-layers

Tutorial Posts

  1. Integrating OpenLayers Map with VueJS: Create Map – Part 1.
  2. Integrating OpenLayers Map with VueJS: Create Layers Panel – Part 2.
  3. Integrating OpenLayers Map with VueJS: Implement Style and legend for vector layer – Part 3.
  4. Integrating OpenLayers Map with VueJS: Open Feature Information Popup on click – Part 4.
  5. Integrating OpenLayers Map with VueJS: Recreating the project with Vite, Pinia and TypeScript-Part 5.
  6. Integrating OpenLayers Map with Vue.js: Creating Vector Tiles, Adding VectorTile Layers, and Implementing Dynamic Styling – Part 6.

This template should help get you started developing with Vue 3 in Vite.

Recommended IDE Setup

VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).

Type Support for .vue Imports in TS

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:

  1. Disable the built-in TypeScript Extension
    1. Run Extensions: Show Built-in Extensions from VSCode's command palette
    2. Find TypeScript and JavaScript Language Features, right click and select Disable (Workspace)
  2. Reload the VSCode window by running Developer: Reload Window from the command palette.

Customize configuration

See Vite Configuration Reference.

Project Setup

npm install

Compile and Hot-Reload for Development

npm run dev

Type-Check, Compile and Minify for Production

npm run build

Run Unit Tests with Vitest

npm run test:unit

Run End-to-End Tests with Cypress

npm run test:e2e:dev

This runs the end-to-end tests against the Vite development server. It is much faster than the production build.

But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):

npm run build
npm run test:e2e

Lint with ESLint

npm run lint