SpinViewer with latest Vue3 does not work in production builds
See original GitHub issueDescription
When trying to use SpinViewer in latest Vue3 production build, it is unable to get it’s props. In debug build, the following message appears in console:
[Vue warn]: Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.
| PublicInstanceProxyHandlers.ownKeys | @ | runtime-core.esm-bundler.js?d2dd:3252
| getValidProps | @ | view360.esm.js?562e:7346
| mounted | @ | view360.esm.js?ffb2:144
This happens in getValidProps
method.
Steps to check or reproduce
Try to use in production build with Vue3.
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Vue3 project not working after vite build in production mode
I have a project that works fine when running in development mode, but if I build the project using `vite build´, some components...
Read more >Build Targets - Vue CLI
When you run vue-cli-service build , you can specify different build targets via the --target option. This allows you to use the same...
Read more >Production Deployment - Vue.js
When deploying to production, we should drop all the unused, development-only code branches for smaller payload size and better performance. Without Build Tools ......
Read more >Quick Start - Vue.js
If you are already familiar with Node.js and the concept of build tools, you can ... When you are ready to ship your...
Read more >Migration Build
If your app is unfortunately not suitable for upgrade, do note that we are planning to backport Composition API and some other Vue...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just released a new version (v3.0.4) that fixes this issue, try that one!
Sure, as soon as the review is finished