-
-
Notifications
You must be signed in to change notification settings - Fork 255
Typecast in Vue SFC prop results in Babel error? #740
Comments
Quick note (walking away from the computer always spawns new thoughts): in this case the import mitt from 'mitt'
... snip ...
props: {
eventBus: {
type: mitt,
required: true
}
} works around the problem, but for future use I'd like to know how to do the type cast as well... (Vue complains about a prop type mismatch at runtime, but does work) |
Hm... Seems like something funny is going on with my babel-loader:
Ah ha! While I thought this wasn't related to Vue 3, of course I'm using vue-loader 16.0.0-beta5... that could easily be the source of these bugs! (to be clear, I haven't confirmed that, but it seems highly likely) |
Downgrading to Vue 2 and vue-loader 15.9.3 did not fix the issue. |
There's probably something going on with the default babel preset, I still need to investigate this furthur. |
Thanks for keeping up with this. Looks to me like I'm running into babel/babel#6959, where babel is trying to interpret <...> as TSX. That lead me to poi/plugin-typescript, which worked but needed an update to fork-ts-checker-webpack-plugin to support Vue 3 (it worked but spewed errors because I don't have vue-template-compiler installed). I hacked together an update that works for me. There were some old config values that I couldn't figure out how to update, so it's probably not pull request ready. Let me know what you think. Reading the Poi and Babel docs it seems like I might be able to disable enough TSX functionality to also work around the problem (the Babel issue has some tips), but I don't think I actually need Babel right now, so I'm happy with plugin-typescript. |
This issue has been marked as Stale, it will be closed in a week if there's no furthur activity. |
As I mentioned above, my temporary fix was to patch ts-checker to a newer version than Poi shipped with. Unfortunately my long term solution was switching to Vite because the Vue 2 to Vue 3 transition became a little too complicated with Poi (at the time; it might be easier now...) |
I'm relatively new to web development, so hopefully is a fairly trivial configuration change rather than a bug, but here goes...
I'm using Typescript in a Vue SFC, and I'm trying to enforce the type of a component property:
This produces an error during
poi --serve
:which lead me to this VueJS Developers post implying Babel needs to be using the Typescript parser (search for "babel eslint parser"), but AFAICT the Poi Babel preset does use the Typescript parser?
My package.json is vanilla (just dependencies), and I'm not overriding any Poi defaults. I am working with Vue 3rc5, though AFAIK this code isn't Vue 3 specific. Other possibly relevant versions:
It seems like I'm close, but obviously still missing something. I will very much appreciate any tips, thanks in advance!
The text was updated successfully, but these errors were encountered: