Closed andycodesstuff closed 5 years ago
All of the error related code that I created to test this scenario is contained in the commit named "vue-overdrive test" (the latest one)
@andrycodestuffs Thanks for reporting these issues.
As for the warning you mentioned, I'm honestly not sure what's causing that. I'll have to do some investigating.
As for the TypeError
, there's actually an open issue with Ramjet (the library I'm using under the hood for animations) where you can't tween percentage based border radii: https://github.com/Rich-Harris/ramjet/issues/57. Change border-radius: 100%;
to a pixel value and it should work 😅
Quick update. I just scaffolded a vue-cli
project, added vue-overdrive
, and I'm not seeing that warning (Critical dependency: the request of a dependency is an expression
). Could this be related to another dependency in your project?
You were right!
The error was caused by the percentage-based border radii, sorry for bothering.
Speaking about the warning, vue-overdrive
is the only dependency that I installed after creating the project and I can confirm that the warning comes from it.
I'll do some research about it and if it's a vue-overdrive
related issue I will let you know
Don't be sorry, that's totally my fault for not calling that out. I've added a note to the README so that others don't fall in the same trap.
Please do let me know if you find anything re: that warning. I welcome PRs ❤️
I tried the latest version of vue-overdrive
on Windows 10 with the same result (the dependency is an expression
warning), this time I created a new Vue project using the same configs as before and just imported vue-overdrive
with the following line: (to be sure that it was the real cause of the warning)
import Overdrive from 'vue-overdrive'
My setup:
I'm going to deeply investigate the question and propose any solutions that I can find
I made some progresses.
I cloned the repo and used vue-overdrive
directly by importing the files in the test app and I noticed one thing: the warning doesn't appear when you import the "uncompiled" development version of vue-overdrive
that is:
import Overdrive from 'path/to/vue-overdrive-repo/src'
But it pops up when you import the production version (of course) so it may be related with Parcel bundling options
Expected Behavior
The
overdrive
component should morph the given elementsActual Behavior
stack trace:
Steps to Reproduce the Problem
@vue/cli
using the following configurations: 1.1. Manually select features 1.2. I selected:Babel, TypeScript, Router, Vuex, CSS Pre-processors and Linter / Formatter
1.3. Use class-style component syntax? Y 1.4. Use Babel alongside TypeScript for auto-detected polyfills? Y 1.5. Use history mode for router? Y 1.6. I picked SASS/SCSS pre-processor 1.7. I picked TSLint for linting and removed any selection in the next option 1.8. Where do you prefer placing config for Babel, PostCSS, ESLint, etc.? In dedicated config filesvue-overdrive
withnpm install --save vue-overdrive
N.B. When building the project (for development or production) the following warning shows up:
Specifications