I have a folder structure like this
--Page
-group.vue
--Services
-groupMixin.ts
script of group.vue
<script lang="ts">
import { Vue, Component, Mixins } from 'vue-property-decorator'
import { GroupMixin } from '../../services/groupMixin';
@Component
export default class Group extends Mixins(GroupMixin) {
created () {
console.log(this.test)
}
}
</script>
code of groupMixin.ts
import { Vue } from 'vue-property-decorator'
//creating mixins.
export class GroupMixin extends Vue {
test: string = 'sss'
}
I am facing two problems here.
First, to import a ts file i used ../../, is there any way to use ./ or @/. Without using lang="ts", i can import a js file like this @/services/...
Second, not able to access the varaible test which i declared in groupmixin.ts.
Please try to do the following to make your mixin to work:
group.vue
groupMixin.ts
There is a reason that I am using importing
Vue
usingimport Vue from 'vue';
, it is mainly because some IDE's are highlighting Vue functions like$emit
when it is imported fromvue-class-component
.As for import ts files if you are not using
vue-cli
you'll need to setup webpack's resolve alias and also in yourtsconfig.json
and possibly will need to use tsconfig-pathsI spent a lot of time today trying to figure out how to get Vue mixins to work in a TypeScript project. Apparently all the normal ways that the tutorials say to use mixins simply do not work in TypeScript. The components don't have access to the properties defined in their mixins because apparently the Vue framework's mixin code just isn't TypeScript-friendly.
Eventually, I did find a way to get mixins working in TypeScript. Working really well, in fact. I have multiple levels of mixin inheritance in my project, with mixins extending other mixins, and it all works exactly how I expected it to. The secret was that I had to install this third-party package that someone wrote to fix mixins in TypeScript:
https://www.npmjs.com/package/vue-typed-mixins
Couple words of warning (but neither is a big deal):
This plugin only works for me if I define my mixins in .ts files instead of .vue files. This wasn't a problem for me because my mixins only contain code, no html or css (and I can't think of a situation where that would even make sense).
When you include a mixin on a component, make sure you do it the same way as the example on the package's website (url above). If you simply install the package without refactoring your code to follow the example on the site, it won't work.
Here's a simple example:
Which is then used by: