Additional Extensions not filled by @nuxt/typescript-build

[b-m-f]

Version

v2.10.1

Reproduction link

https://toomuchwork.com

Steps to reproduce

• setup @nuxt/typescript-builder
• Start nuxt programatically. const nuxt = new Nuxt => new Builder(nuxt)
• https://github.com/nuxt/nuxt.js/blob/92c7f4ed249466870a477798f910c84eb1fdd18d/packages/builder/src/builder.js#L47 will be empty. Should be ['ts', 'tsx']

What is expected ?

additionalExtensions should be ['ts', 'tsx']

What is actually happening?

additionalExtensions is []

_{This bug report is available on Nuxt community (#c9924)}

[kevinmarrec]

@b-m-f You need to do await nuxt.ready() AFAIK so it properly setup the module (it will call the module container that is responsible to register modules).
Without doing it it will trigger the build without having called @nuxt/typescript-build so you won't have additionalExtensions properly set.

Alternatively, you can also register the TS @nuxt/typescript-build module this way : https://github.com/nuxt/typescript/blob/master/packages/typescript-build/test/module.test.ts#L36

[b-m-f]

Thanks. Will try it out on wednesday when I am back on the codebase. Seems like this will likely be the culprit! It did smell like an Synchronization problem :)

[b-m-f]

@kevinmarrec This was indeed the problem. Is there a place I could add some documentation for this?

[kevinmarrec]

@b-m-f I think it's related to #139 request, i'd say new Guide section about Programmatic usage

[chanlito]

Ok, so took me like an hour to figure out why middleware wasn't picking up .ts files until I stumbled upon this issue.

Current solution for me is to add additionalExtensions: ['ts'] in the nuxt.config.js build object.

I think the default option should include .ts files.

BTW: I'm using Nuxt programmatically.

[kevinmarrec]

Closed by #233