Skip to content
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

fix: do not use fork-ts-checker-webpack-plugin for vue-next #5172

Closed

Conversation

cexbrayat
Copy link
Member

Probably a better alternative to #5170

As the fork-ts-checker-webpack-plugin tries to load the compiler, it does not play well at the moment with the vue-next compiler @vue/compiler-sfc. This disables the plugin if we are building a vue-next project.

See vuejs/vue-cli-plugin-vue-next#5 for context.

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Underlying tools
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

Other information:

@cexbrayat cexbrayat force-pushed the fix/ts-vue-next-do-not-use-fork branch from 2186023 to 63f16f0 Compare February 9, 2020 19:14
As the `fork-ts-checker-webpack-plugin` tries to load the compiler, it does not play well at the moment with the vue-next compiler `@vue/compiler-sfc`. This disables the plugin if we are building a vue-next project.
@sodatea
Copy link
Member

sodatea commented Mar 19, 2020

Closing this as #5170 has been merged.

@sodatea sodatea closed this Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants