-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with TypeScript #28
Comments
It is also not clear how to setup TypeScript build. @nles can you please share your recipe? |
I am especially asking about |
TS support of nuxt is still experimental. After stablizing, we will work on supporting it. For now, you can simply use |
/cc @kevinmarrec |
@nles For @pi0 Sorry I've 0 knowledge around |
I was not able to resolve this issue:
Setting explicit Here's my template if you want to try the same setup: https://github.com/wemake-services/wemake-vue-template (rename |
i think problem is we need it load as typescript startStep('Nuxt build')
// Read nuxt.config.js
const _esm = esm(module)
const nuxtConfigFile = _esm(path.resolve(rootDir, nuxtConfigName)) |
This should be fixed by #129 in the next release. |
Hi @danielroe, thanks for the update! Do you have any idea when the next release may happen? |
@vimota Now released 😄 |
Also my apologizes for this delay. |
Trying out this builder for a Nuxt + TypeScript project.
Got bunch of these kind of TS errors during build:
Apparently caused by how the now build step will have the node_modules symlinked to node_modules_dev, and how ts-node handles symlinks (TypeStrong/ts-node#396).
One quick solution is to add NODE_PRESERVE_SYMLINKS environment value to the execution of nuxt build (like this: nles@fce3630).
Also, in your tsconfig.json file you'll need to have:
Probably not the best solution to the problem, but leaving this here if someone else is having issues with TypeScript support and needs a solution.
The text was updated successfully, but these errors were encountered: