The type of this.previousPieceSelected is inferred from the initial state, and it’s currently initialized to undefined, so it thus has a type of undefined (meaning it can only be assigned a value of undefined). Use type assertion on the initial undefined value (i.e., the as keyword plus the desired type of Piece | undefined). Also … Read more
You can use ref to reset the file uploader value. this.$refs.fileupload.value = null; codepen – https://codepen.io/Pratik__007/pen/MWYVjqP?editors=1010
I had exacly the same problem and just figured it out, I hope this helps someone. First I changed the vue template compiler to: “vue-template-compiler”: “2.6.11” and the I also had to change the vue version to the latest realese, in my case: “vue”: “2.6.11”
I had this same problem and realize that despite of no having errors on my IDE, the error was still thrown so I just Restart the server and it works perfectly… I have to do this every time I created a import or export anything with TS.
Arguably, the error message could be improved on this one. The error was caused by trying to iterate through a non-iterable (in your case undefined), using v-for. Specifically, before the call made in mount() returns, product.product_images is undefined, because you initiate product as empty object. Vue 2 style solutions instantiate product.product_image as iterable: //… data: … Read more
You can use vite-plugin-dts import dts from “vite-plugin-dts”; export default defineConfig({ plugins: [ dts({ insertTypesEntry: true, }), ],
try it. <script lang=”tsx” setup> import { h } from ‘vue’; const render = () => { return h(‘div’, []); }; const jsxNode = () => { return <div> text </div>; }; </script> <template> <render /> <jsxNode /> </template>
The error means that structuredClone was executed on Proxy instance, which cannot be cloned. In order to allow this, it should be used on raw object that a proxy wraps: const b = structuredClone(toRaw(a.value)); Notice that toRaw is used on a.value because both a and a.value are reactive objects, and toRaw works shallowly and needs … Read more
Registering components in the root component’s components option doesn’t make them global. Doing that just makes them available to the root component itself, not its children. To register components globally, use app.component in your top-level code: main.js import { createApp } from ‘vue’; import App from ‘./App.vue’; import MyGlobalComponent from ‘./components/MyGlobalComponent.vue’; const app = createApp(App); … Read more
I had the same issue and this change fixed the issue. In your .eslintrc.js file, add requireConfigFile: false parserOptions: { parser: ‘@babel/eslint-parser’, requireConfigFile: false, // <== ADD THIS ecmaVersion: 2018, // Allows for the parsing of modern ECMAScript features sourceType: ‘module’ // Allows for the use of imports }