Closed aefika closed 4 years ago
I´m having the same issue. Have you fixed it?
I haven't touched it. It seems that this upgrade requires several modifications in CSS and methods. I guess that's why CreativeTim has not answered. https://popper.js.org/docs/v2/migration-guide/
Also, heads-up for several packages included in \public\material\js\plugins, they are outdated but working. I've updated manually several of them to be sure to be up to date: moment (also included the locales), sweet alert, chartist and bootstrap-switch. The rest is probably outdated but not using them personally.
This is very strange. 30 minutes ago I sent the repo to a friend, he cloned it and everything went ok. He didn´t touch anything but for some reason it worked. Anyway if I find the answer I will let you know and thanks for the info above.
@aefika I "find" the solution. Seems that npm is not as good as yarn in poor connections. So I'm not sure how good is your internet but just in case, try using yarn instead of npm.
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Please describe the behavior you are expecting On npm install, I'm expecting no warnings for deprecated: npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 Please provide instructions to upgrade
Current Behavior
What is the current behavior? npm WARN deprecated popper.js@1.16.1