-
Introduction
- Understanding Matomo
-
Matomo Core development
- Contributing to Matomo Core
- Contributing to Matomo Plugins
- Coding Standards
- Using GitHub Issues
- Pull Requests and Reviews
- The Core Team Workflow
- Maintaining Plugins
- Maintaining Translations
- Matomo APIs
- Debugging Core
- Profiling Code
- Reproducing Issues
- FAQs
- Core Components
- Composer dependencies
- Release Management
- Using GitHub Actions
- Matomo's Roadmap
- Matomo Plugin development
- Web Interface
- Utils
- Reporting API
- Data Model
- Tests
- Tools
-
Plugin Development
This documentation is for an outdated Matomo version.
Click here if you want to read this article for the latest version.
Click here if you want to read this article for the latest version.
Troubleshooting common Vue issues
TypeScript complains component computed property does not exist
This error occurs sometimes with Vue components that have no props entries where
for some reason, Vue will not add computed properties to the component's this
type, so expressions like this.myComputedProperty will result in errors.
This can be fixed by adding explicit return types to your computed properties, for instance:
export default defineComponent({
computed: {
myProperty(): string {
return 'test';
},
},
})