-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use anime.js with node and express #869
Comments
Hmm, yeah I think the target type detection is confused by the environment. |
Here is the link to the code: |
Can you try |
I am still getting the 500 internal server error (a.hasOwnProperty is not a function), with the same call stack being displayed along with it. The script isn't even loading. I tried using an alert message, but nothing came on the screen |
Sorry, by removing the |
It's really hard for me to see why this error occurs even if you don't call anime.js?. |
I found a work-around. Went to
Is it a good practice and is it unethical if I do it this way while pushing the software in production? Not that I am pushing it in production or anything, it's just a UI project for my portfolio, and I just wanted to use the library because it seemed great. Is it okay if I go with this, and are there any cons associated with doing it this way? Thanks! |
Well now I'm even more confused...
It should be fine! |
I am sorry for causing any confusion 😅. Here is the link to the repo, in case you want to have a look |
I'm glad it's working! |
a.hasOwnProperty is not a function
after importing animejs js into my node environment using
import anime from 'animejs'
and registering it as a middleware with express usingapp.use(anime)
as soon as I start the server, I am getting the following errorTo Reproduce
Steps to reproduce the behavior:
npm install animejs --save
Expected behavior
The element should be animated. The reason might be
a
being expected to be an object which might be actually not. And callinghasOwnProperty
on a non-object might be causing the issue. I tried debugging the codebase but this is only what I could understandScreenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: