You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Vue.use(CoreuiVue); from @coreui/vue/src per the pro admin template.
npm run dev
Expected
The project should compile without error.
Saw
🚨 /[path to project]/node_modules/@coreui/vue/src/components/table/CDataTable.vue: v-else used on element <td> without corresponding v-if.
at VueAsset.compileTemplate (/[path to project]/node_modules/parcel-bundler/src/assets/VueAsset.js:152:15)
at VueAsset.postProcess (/[path to project]/node_modules/parcel-bundler/src/assets/VueAsset.js:100:26)
at Pipeline.processAsset (/[path to project]/node_modules/parcel-bundler/src/Pipeline.js:90:31)
at async Pipeline.process (/[path to project]/node_modules/parcel-bundler/src/Pipeline.js:24:23)
at async Object.run (/[path to project]/node_modules/parcel-bundler/src/worker.js:15:12)
at async Child.handleRequest (/[path to project]/node_modules/@parcel/workers/src/child.js:60:26)
The only reason I can think of for the discrepancy between Parcel and Vue CLI behavior that came with the template is that the error Parcel is choking on is technically only warning. Whether we consider it an warning or an outright error, it’s:
Breaking Parcel.
Not great code because the v-else is not on a matching element type.
Easily remedied by using another v-if with a negated version of the same condition.
The text was updated successfully, but these errors were encountered:
adamshaylor
added a commit
to pollinate/coreui-vue
that referenced
this issue
Apr 7, 2021
npm init
on an empty directory.npm i --save @coreui/[email protected]
Vue.use(CoreuiVue);
from@coreui/vue/src
per the pro admin template.npm run dev
Expected
The project should compile without error.
Saw
The only reason I can think of for the discrepancy between Parcel and Vue CLI behavior that came with the template is that the error Parcel is choking on is technically only warning. Whether we consider it an warning or an outright error, it’s:
v-else
is not on a matching element type.v-if
with a negated version of the same condition.The text was updated successfully, but these errors were encountered: