-
Notifications
You must be signed in to change notification settings - Fork 189
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
importing popmotion from node_modules #61
Comments
Hi @Andrew-Bootsma, It sounds like this might be related to a bundler issue. Have you followed the following instructions on Brian's course website? |
Thank you for the response @laniehei I have repeated the necessary steps from the link that you sent and I am still getting an error. The error message is now
|
Hi @Andrew-Bootsma, First, I would try to delete your node modules and reinstall. If this doesn't work, it seems like it's having an issue with the styler package within Popmotion. Do you have |
Having the same issues. In the end I gave up. Not sure what the issue is but yeah, it doesn't work through node for some reason, |
hey @Andrew-Bootsma @FarfamaH I had the same issue, fixed it with changing the dependency in the package.json to |
In lesson
Building Your Code with Node.js
I am getting an error after removing the unpkg script tag from the HTML file and replace it withimport popmotion from "popmotion"
in my JavaScript file.The error I am getting from the dev tools console is
Uncaught TypeError: Error resolving module specifier “popmotion”. Relative module specifiers must start with “./”, “../” or “/”.
I found this issue on Stack Overflow --> https://stackoverflow.com/questions/63623432/uncaught-type-error-when-i-am-using-npm-install-popmotionit-is-used-for-animati, which I believe is a student having the same error. They get a different error message, but I think that is because they don't test their code until after they build, just as you do in the lesson. If I build my code with the error, I get the same error message as them.
The text was updated successfully, but these errors were encountered: