generation fails if sfc has additional type/interface/class declarations

[lucastheisen]

As a simple example, this sfc:

<template>
  <div>{{ foo }}</div>
</template>

<script lang="ts">
import Vue = require('vue')
import Component from 'vue-class-component'

type Foo = string;

@Component
export default class TsClass extends Vue {
  foo: Foo = 'Hello'
}
</script>

<style>
div {
  color: red;
}
</style>

Will not generate a *.vue.d.ts file. A little digging shows that the following line in language-service.ts:

    const output = this.tsService.getEmitOutput(fileName, true)

Will emit

{
  "outputFiles": [],
  "emitSkipped": true
}

I have a unit test demonstrating this, and can provide as a pull request if you would like, but it would break the CI unless you fixed this issue...

[ktsn]

I guess this is because Foo type is not exported while it is used in component type. As we generates declaration files, we cannot use private types in a part of exported types.

[lucastheisen]

@ktsn , I modified the following change:

--- a/test/fixtures/ts-class-with-additional-type.vue
+++ b/test/fixtures/ts-class-with-additional-type.vue
@@ -6,7 +6,7 @@
 import Vue = require('vue')
 import Component from 'vue-class-component'

-type Foo = string;
+export type Foo = string;

 @Component
 export default class TsClass extends Vue {

It still fails in the same manner. If you would like, I could submit a pull request for this unit test... Or you can tinker with my fork (specifically the genfail branch)

[ktsn]

PR for unit test is welcome 🙂

[lucastheisen]

Supplied: unit test for generation fails if sfc has additional type/interface/class declarations #12

[ktsn]

See #12 (comment)